I think the issue was mitigated by just changing the setup script to bash. For whatever reason now seems to work.
to improve our project for newcommers, I did the following:
created a VM setup using vagrant (with a full botstrap script)
added a "setup guide" doc (with the previous installation instructions from readme, plus a couple more infos)
added a notice about the possible seed issue and how to test and solve it.
A very important thing to notice: I've changed the default db/user/pass on .env to reflect the "metadataregistry" rebranding. So if anyone is relying solely on this file to set the user/pass/db they will receive connection errors when trying to run anything. To fix, just add your specific settings on .env.local
refer to #36
I think the issue was mitigated by just changing the setup script to
bash. For whatever reason now seems to work.to improve our project for newcommers, I did the following:
seedissue and how to test and solve it.A very important thing to notice: I've changed the default db/user/pass on
.envto reflect the "metadataregistry" rebranding. So if anyone is relying solely on this file to set the user/pass/db they will receive connection errors when trying to run anything. To fix, just add your specific settings on.env.local