You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that when the database is behind a firewall, and the rails server cannot make any network request to the database, kamal setup fails by the rails server not starting.
There was no error message saying during the kamal setup command that indicates that. And when you try to go into the VM that hosts the rails container, and you do something like docker logs container-name, there's no logging at all.
Would it be possible to say something like connection timeout error or something to say the db:create failed because the server is unreacheable instead of being silent about this error?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I noticed that when the database is behind a firewall, and the rails server cannot make any network request to the database,
kamal setup
fails by the rails server not starting.There was no error message saying during the
kamal setup
command that indicates that. And when you try to go into the VM that hosts the rails container, and you do something likedocker logs container-name
, there's no logging at all.Would it be possible to say something like connection timeout error or something to say the
db:create
failed because the server is unreacheable instead of being silent about this error?Beta Was this translation helpful? Give feedback.
All reactions