Closed AliAbstract closed 2 years ago
Thanks for this report, I'll take a closer look at what might be going on here. Unfortunately it probably will take me a little while since I'll need to find a time when it is safe to start with a fresh DB to see if I can reproduce. If you make any progress in the meantime let us know :)
This was fixed up a while back from what I can tell.
Issue Description: When running the init-db.sh script (as described here, the following warnings/errors occur.
First, when attempting to create a Node.js instance, the following deprecation warning is given.
Second, during
+ docker-compose run --rm -e PYTHONPATH=docker/ --entrypoint 'poetry run ./manage.py shell -c "import testdata"' django
, the following error can be found:You can see the cause of the error below; there are two sites (example.com and openstates.org). If you remove example.com,
I have tried running ./docker/init-db.sh multiple times, and originally I would get an error that there were multiple user accounts with the same information (I assume this is because I ran the command multiple times).
Fixing this error is easy enough (see below), but I continue to receive the sites error.
I've included the full output of a run after I have deleted both the extra example.com site as well as the local user to have as clean of a run as possible. It does end up working, but it might be worth examining why "example.com" is returned from the original run from scratch. It also shows other warnings/info messages that might be worth investigating as well.
URL where this issue may be seen (API or OpenStates.org): When attempting to create an instance of OpenStates.org for local development following these steps: https://docs.openstates.org/en/latest/contributing/running-the-site.html