Initialize the database issue on DigitalOcean droplet about citizenlab HOT 5 CLOSED

Thanks for reporting @jamwithsam

We're releasing a new image very soon, probably tomorrow, that resolves the issue. It depends on this PR: #221 getting merged.

from citizenlab.

A new image has been released that resolves the issue with the database commands.
First, pull in the new images

docker-compose pull

Then retry the command

docker-compose run --rm web rake db:create db:migrate db:seed

If it still doesn't succeed, you can try deleting your database folder to start over with a clean database by deleting its folder

rm -rf postgresql-data

from citizenlab.

Thank you for the update and fix @kogre

The database initialization was successful after the update

from citizenlab.

I noticed I had an ERROR: 1 when running the command again docker-compose run --rm web rake db:create db:migrate db:seed

and its as followed:

W, [2021-05-13T15:04:34.725435 #1] WARN -- #<Bunny::Session:0x55c9c27c26f8 guest@rabbitmq:5672, vhost=/, addresses=[rabbitmq:5672]>: Could not establish TCP connection to rabbitmq:5672: Connection refused - connect(2) for 172.18.0.4:5672
Database 'citizenlab' already exists

is this okay @kogre?

from citizenlab.

Great that it got resolved!

Yes, this is okay, it's startup timing issue between containers, but which resolves itself.

from citizenlab.