Open skobkin opened 8 months ago
You're completely right that it should be possible to re-run this command safely! We should fix that.
As an intermediary fix just to get you moving for now, it looks like the database setup part worked correctly and the command stopped at collectstatic
, so you should be able to address the issue with collectstatic
(it sounds like it might have been an s3 config thing?) and then just run
./bw-dev collectstatic
./bw-dev admin_code
And that should get you the rest of the way through the command
Sorry, I wasn't able to check if your fix works out. As I didn't have anything that should be preserved in the database yet I just pruned Docker volumes and started again without S3 to try to move to it later when I have more time. It worked as expected.
But thank you for a quick reply!
Describe the bug I most likely had a problem with S3 configuration when running
./bw-dev setup
.It ended with:
I probably fixed the problem and to check that I ran
setup
again. But nowsetup
can't set up the instance already because some keys were already persisted in the database:Expected behavior Properly processing setup procedure if it is running again after failure
Instance Is not online yet.