Some modifications for anyone wanting to run this in 2025 #322
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know this repo hasn't been updated in a while, but I tried to run it with Docker and ran into a few problems. I found out that I needed to lock Mongo to a specific version, ignore Node version warnings and keep it at node:carbon (which is v8), and had to change some things to package.json since one of them is now a public Github archive.
I'm ignoring engine warnings when running
yarn installbecause some packages need to be at Node version 12, but there are some errors regardinguwsthat can only be solved by being at node version 8. So I was caught in a cat-and-mouse situation.If anyone is simply trying to get this running in 2025, I hope this PR is helpful in some capacity.