Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Self-hosted privacy policy, terms of service and code of conduct #2408

Open
2 tasks
ojeytonwilliams opened this issue Feb 22, 2023 · 1 comment
Open
2 tasks
Assignees
Labels
Projects

Comments

@ojeytonwilliams
Copy link
Contributor

People who self-host chapter will need a way to provide their own versions of these.

As @allella mentioned #2373 (comment) the simplest approach would be to leave them as links, but allow them to be customised.

There are two main tasks

  • Persist the URLs
  • Use the URLs instead of the hard-coded values

While the best UX is probably to provide a GUI to customise the variables (and persist them in the database) the simplest approach (sufficient for the MVP) would be to store them in environment variables.

@ojeytonwilliams ojeytonwilliams added MVP Discussion Ideas, feature requests, views on features. Anything which is a discussion. labels Feb 22, 2023
@ojeytonwilliams ojeytonwilliams added this to Code in MVP Feb 22, 2023
@ojeytonwilliams
Copy link
Contributor Author

ojeytonwilliams commented Feb 22, 2023

Thinking about it, since there's a fair bit of site configuration, it might be best to create a dashboard page. It's more effort, but I think it's probably worth it given how many environment variables we would end up with. Also, having to redeploy the site to fix a typo in the description would be frustrating.

@Sboonny Sboonny removed the Discussion Ideas, feature requests, views on features. Anything which is a discussion. label Feb 22, 2023
@Sboonny Sboonny self-assigned this Feb 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
MVP
  
Code
Development

Successfully merging a pull request may close this issue.

2 participants