-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start with provided instructions. #95
Comments
I made a sample .env file
|
@TheOddball sorry, I'm only seeing this now. I didn't know anyone was really looking at this code 😅 The .env provided by @alyssadev is great! It matches quite well what I have in my own Did you get it to work? Unfortunately, I'm in the middle of a big rework of the back-end at the moment. The API that was relied upon, Universalis, has changed their format and the structure of their responses. I'm not sure if the current code will update properly. Overnight, it suddenly started returning empty responses or missing prices. Without adjusting the "fetcher", "updater" and "database" services, I'm not sure how usable it is. I'm actively working to fix it daily. |
@TheOddball @alyssadev If you get a chance, can you try again please? This should work directly: It takes about a minute for the database to start, then on |
I am trying to get GilGoblin working under docker, and unfortunately I am having issues getting it started with the provided instructions.
I am using a brand new install of Ubuntu 24.04 (or 22.04) on a VM (except for installing docker-compose), and running
docker-compose up -d
is failing to start the containers, failing due to invalid variables (complaining most about ports).Setting the ports manually in the docker-compose will not get it to load either, due to another error:
'name' does not match any of the regexes: '^x-'
Running the compose using the plugin version (using
docker compose up
) does get it to start, but most if not all of the containers are failing due to numerous errors. (I imagine due to missing variables.)Thank you!
The text was updated successfully, but these errors were encountered: