Why is output specified in config and also hardcoded in source? #2

Closed
opened 2025-05-01 10:35:32 -05:00 by ITwrx · 1 comment
Owner

It looks like site.output is read from config, but never used. We probably started one way, changed course, and forgot to reconcile/clean up the old approach. output config item and related code was probably supposed to be removed for the hardcoded approach. If we do want the output location to be configurable, in case people wanted to run as different users with diff perms on log and report location, output needs to be used just for location, and not the whole output file name, as it currently is. Right now, the source code is using a hardcoded location, and generating the output file name with date included, which is better than a config'd static output file name with no date. This definitely got missed/not cleaned up.

It looks like site.output is read from config, but never used. We probably started one way, changed course, and forgot to reconcile/clean up the old approach. output config item and related code was probably supposed to be removed for the hardcoded approach. If we do want the output location to be configurable, in case people wanted to run as different users with diff perms on log and report location, output needs to be used just for location, and not the whole output file name, as it currently is. Right now, the source code is using a hardcoded location, and generating the output file name with date included, which is better than a config'd static output file name with no date. This definitely got missed/not cleaned up.
ITwrx added the
design flaw
enhancement
labels 2025-05-01 10:35:32 -05:00
Author
Owner

Removing config item and related code for now. One less thing that can go wrong during user setup.

Removing config item and related code for now. One less thing that can go wrong during user setup.
ITwrx closed this issue 2025-05-01 11:01:49 -05:00
ITwrx added the
fix in dev
label 2025-05-01 11:02:01 -05:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ITwrxOrg/GoAccessReporter#2
No description provided.