I am trying to get Leantime running with a YAML and running into issue after issue, I have come across too many to list, been trying for over an hour now.
I am wondering if anyone has this running in TrueNAS? I am using Scale Goldeneye. Not specifically asking to troubleshoot what I have, I am just hoping not to have to reinvent the wheel if someone has it running.
I think you need to start with the basics of what version of TrueNAS Scale Goldeneye. It may make a difference. I am guessing you are working through the Documentation?
Thanks! I am using the YAML provided by Leantime and modified it for my volumes and port. I have several app installed by YAML that are not in the catalog and I have been able to work through issues to get them working. This one I cannot.
Again, not looking to troubleshoot what I am doing, looking to see if someone has it working and can provide how they were able to.
So this is the YAML I am now using, after about 45 minutes of me adjusting it, I last resorted to AI to try and help me (Yeah I know). At this point this is about 37 (in a row?) adjustments working with Gemini. It is very possible it’s all jacked more now than when I started.
Currently the app shoes both the db and service containers are running but I cannot access them via browser, returns “Refused to connect”.
ok so the ai already removed the .env file and and uses plain environment variables in the yaml. that removes one concern i had.
I’ll propably give it a go with a test install when i’m home from work (don’t judge me for answering forum posts during work hours, i have literally 0 customers right now…)
@DjP-iX No this is how it pasted. If the indents are not right TrueNAS won’t let you save the YAML
@LarsR Thanks. Yeah AI can work well or blow it up like walking out of a Taco Bell bathroom. I am still working with it, feeding the logs from the container. It just had me switch to Maria and set the user as root (yes I know but I am really testing at this point, no intensions of leaving it like that).
It appears that somewhere along the lines, 8080 was changed to 80 in the YAML and I did not notice. Once corrected, it’s working. It’s always something dumb like that. My bad, thanks!