Closed nwalters512 closed 1 year ago
Is there any known fix for this issue at this point in time? I've tried everything from downgrading node with nvm
and running with node 8, to manually installing all dependencies (yes, this did take an extensive amount of time, 10/10 would not recommend), with no luck yet. Any fix for this yet?
Same problem here.
I hate to say it but I feel like this project is abandoned. It hasn’t had any updates all summer, and you would think that in the midst of a global pandemic where all schools are practically moving to online instructions, there would have been some commit history or some update. But I think this one is unfortunately dead. It was great while it was being maintained though.
This issue is happening because of a change with the database configuration. We currently use environment variables for all configuration, which is documented in the README. I now realize the README doesn't make this change completely obvious, so I restructured it here: https://github.com/illinois/queue/tree/update-env-documentation. Please let me know if this change makes things clearer!
Is #324 related?
I'm taking a look at getting things functioning again this weekend. It's generally poor practice to require devs to set up specific config after cloning a project, i.e. add a .env
file with specific values. npm ci && npm run dev
should be all you have to do.
With that in mind, I'm going to refactor the config to look for .env.{NODE_ENV}
files so that we can safely commit a .env.development
file with standard sqlite config.
Description
When running from a freshly-cloned copy of master, it crashes on startup:
My guess is that this is related to the removal of
src/config
in https://github.com/illinois/queue/pull/288. If additional steps are necessary to configure the repo after cloning, those should be documented.Steps to reproduce
npm ci
.npm run dev
.