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
When a person builds a docker container, he probably think of it has a safe operation that does not modify stuffs outside the container. Now if for any reason the code is modified to connect to an online database, running the migrate command will migrate and modify the online database. This can be dangerous at it may be used by another raposfly instance running in production for example, and people will not think of it as a side effect when running docker build.
I think the migration should be handled in another way, I'm not sure which one yet, but I'll think about it.
raposfly/services/backend/Dockerfile
Line 45 in 60dc189
Not sure Dockerfile should apply migrations.
The text was updated successfully, but these errors were encountered: