Issue Adding Sets #20
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: FrederikBaerentsen/BrickTracker#20
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've loaded the pre-built docker image into Dockge successfully and I can get to the web interface, however when I go to add a set it doesn't seem to actually do anything and just hangs. The "Get set info" text appears but nothing else.
This is the log from the container:
I've tried to load this from an in-house Dockge install running on my TrueNAS instance, and also on a brand-new DigitalOcean droplet. I get the same error on both (the above error log is from the DO Droplet, 111.111.111.111 is the placeholder DO IP address, 222.222.222.222 is my placeholder home IP).
From what I can tell, the .env file with the API key is loaded into the correct folder in the container.
This is the compose.yaml file if that helps:
I'm probably doing something stupid, but if anyone can point me in a direction, that would be much appreciated!
It's probably related to #19, and you need to:
mkdir static/minifigs
- ./static/minifigs:/app/static/minifigs
I have updated the compose.yaml, but unfortunately, that doesn't appear to have fixed the issue.
I have attached an image of where it gets stuck.
Did you add the
.env
file with your rebrickable API key?Yep, the .env file was created with my API key.
I have tested the API key and it works perfectly fine outside of this.
I'm using Portainer. I saw this issue and "resolved" it by moving the lines from the .env file into the compose (stack) file under an "environment:" section. Probably not the "right" way to do it but I've been stuck with .env files in Portainer in the past and didn't feel like trying to figure it out again.
e.g.
Yep, this solved it. Thanks @Sock