You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not an issue really, but I wanted to write it down in case somebody else stumbles upon this edge case (I didn't find anything about it yet):
In the docker installation & by default, the logs are written to a file /app/config/logs/homepage.log and subsequently to the host if /app/config/ is a volume as suggested.
On my end I use the environment variable LOG_TARGETS: stdout to disable file logging. This works as intended.
I use the PUID & GUID variables also.
Now I've noticed that, even with stdout logging only, an empty directory /app/config/logs/ is created on container start.
I've also tested it with the logpath setting, ie. log to /tmp instead. This works as intended also, logs are written to /tmp/logs/homepage.log.
But an extra logs-directory is created in the config-directory still.
When PUID & GUID are supplied a logs-directory is created and setup with the permissions.
And this seem to happen loooong before any logpath or LOG_TARGETS is used/checked against.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there,
not an issue really, but I wanted to write it down in case somebody else stumbles upon this edge case (I didn't find anything about it yet):
In the docker installation & by default, the logs are written to a file
/app/config/logs/homepage.log
and subsequently to the host if/app/config/
is a volume as suggested.On my end I use the environment variable
LOG_TARGETS: stdout
to disable file logging. This works as intended.I use the PUID & GUID variables also.
Now I've noticed that, even with stdout logging only, an empty directory
/app/config/logs/
is created on container start.I've also tested it with the
logpath
setting, ie. log to/tmp
instead. This works as intended also, logs are written to/tmp/logs/homepage.log
.But an extra logs-directory is created in the config-directory still.
Having curiosity, I've checked where that might come from and it's probably from here?
https://github.com/gethomepage/homepage/blob/dev/docker-entrypoint.sh#L34
When PUID & GUID are supplied a logs-directory is created and setup with the permissions.
And this seem to happen loooong before any
logpath
orLOG_TARGETS
is used/checked against.So that's that.
Cheers!
Boiled down
docker-compose.yml
example:Container-Log:
Troubleshooting:
PS: Great application by the way!
Beta Was this translation helpful? Give feedback.
All reactions