Docker .env HOMEPAGE_VAR_XXX template variable substitution not working #3422
Replies: 3 comments
|
Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course! Thanks for using Homepage! ❤️ Based on the information provided, it seems that the environment variables To resolve this issue, you should ensure that the environment variables are correctly defined in your Docker environment and that they follow the naming convention required by Homepage. According to the documentation, environment variables must start with Here are the steps you can follow to troubleshoot and fix the issue:
Please let me know if you need further assistance or if there are any specific error messages or logs that you would like me to look into. This comment was generated by Glime. |
|
This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details. |
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
Sorry to post this, I realise this has been a recurring issue and a point of frustration.
I have searched through all previous discussions on this topic and tried everything I can think of, but have not managed to find a solution.
homepage version
v0.8.13 (986a181, May 6, 2024)
Installation method
Docker
Configuration
compose.yaml:
.env
services.yaml:
Container Logs
All environment variables are present when running
docker exec homepage env:Browser Logs
Troubleshooting
When I swap out the
{{HOMEPAGE_VAR_XXX}}variables and input strings directly (as per commented lines inservices.yaml), everything works correctly.I have tried:
docker compose up --build --force-recreateHowever the problem still occurs.
All reactions