Separate static website content into "user" and "system" parts #6

Open
opened 1 year ago by chris · 0 comments
chris commented 1 year ago
Owner

Right now, all static website content is served from one folder. There is no seperation between content required for the site itself, such as stylesheets and images present on all pages, and user content, such as images used in articles.

Upgrading the website currently requires to build a new Nix package and deploy it, while afterwards copying the public/static directory manually into the website's working directory. I'd rather put the content required to run this website into the Nix package as well, while all user content stays where it is right now.

Right now, all static website content is served from one folder. There is no seperation between content required for the site itself, such as stylesheets and images present on all pages, and user content, such as images used in articles. Upgrading the website currently requires to build a new Nix package and deploy it, while afterwards copying the `public/static` directory manually into the website's working directory. I'd rather put the content required to run this website into the Nix package as well, while all user content stays where it is right now.
chris added the
enhancement
label 1 year ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chris/chris-website#6
Loading…
There is no content yet.