Brainstorm site configuration parameters

sphericalpm / lektorium

A pragmatic web content management solution for those with way too many little sites

MIT License

16 stars 3 forks source link

Brainstorm site configuration parameters #8

Closed mvartanyan closed 4 years ago

mvartanyan commented 5 years ago

We need to come up with a data structure for site configuration parameters. There are obvious things such as:

site root domain/location name
repo name to keep the site source code
list of users / user groups allowed to administer the site
list of users / user groups allowed to edit content on the site

but the actual list of individual site config parameters is likely longer. Continue in comments.

mvartanyan commented 5 years ago

member access restrictions to be deployed (paths -> users/groups)

zillent commented 5 years ago

I think, it would be better save this settings into database. Something like SQLite. Especially for users/groups.

AndreiDrang commented 5 years ago

Yep, sqlite will be best idea to store most of this data. But 2 first things(and maybe better) can be stored in site yml-config-file(or in other file format, which we will choice).

mvartanyan commented 5 years ago

Ideally, Lektorium will be completely stateless, with little, short-lived cache of what it observes in git and docker living in memory. This issue was meant to brainstorm what we need to store about sites, not where.

zillent commented 5 years ago

Example of site config. Any suggestions? :-)

example.com.yaml

apatrushev commented 4 years ago

Irrelevant anymore