Standardized recommended deploy state #3

Open
opened 2025-02-10 10:41:05 +00:00 by trysdyn · 0 comments
Owner

I kind of just blatted this code out into the internet with some bad assumptions about deploy state baked in. For example because I use caddy for all the SSL termination, and run on a node that does nothing but stream handling, I just made the project run as the caddy user. Lazy and bad.

I should pull these assumptions out of the code and make them configurable or auto-detect, and recommend using a standalone user for this stuff.

I kind of just blatted this code out into the internet with some bad assumptions about deploy state baked in. For example because I use caddy for all the SSL termination, and run on a node that does nothing but stream handling, I just made the project run as the caddy user. Lazy and bad. I should pull these assumptions out of the code and make them configurable or auto-detect, and recommend using a standalone user for this stuff.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
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: trysdyn/ovenemprex#3
No description provided.