Closed bjkeller closed 3 years ago
I ran the following three times with the same results each time:
clean my system docker-compose down -v (this also removes aquarium_react_db_data) rm .env rm -rf .env_files
start up production ./bin/setup.sh ./bin/production.sh build ./bin/production.sh up
result A:
I get "aquarium_react_db-migrator_1 exited with code 0" in the log, but that does not appear to affect the system
result B:
the db comes up but it does not have seed data
seed the database docker-compose exec backend env RAILS_ENV=production rails db:seed
run the app go to localhost (or localhost:80) try to login with neptune / aquarium123
result:
get an error, but it appears NO request is being sent: NOTHING hits the production log (you would expect to see a "POST" to the backend...) NOTHING happens in the inspector (you would expect to see activity in the "network" tab...)
OK, the nginx configuration is minimal, so could be that the api isn't exposed properly for the frontend.
These should be expected:
I'm going to close this for now
Adds configuration for running v3 Aquarium in production using Docker Compose.
backend/Dockerfile
; a production entrypoint; and the license file. Also disables dns rebinding guard for production since is running behind nginx. Adds configuration to allow running database migration service.frontend/Dockerfile
; and an nginx configuration file to serve the frontend pagesFixes #596 Fixes #592 Fixes #612