Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Canonical paths #227

Open
boyska opened this issue Nov 23, 2015 · 1 comment
Open

Canonical paths #227

boyska opened this issue Nov 23, 2015 · 1 comment

Comments

@boyska
Copy link
Member

boyska commented Nov 23, 2015

Installing libreant is simple, but lot of details are not standardized. If we want to go towards easier installation, one of the things to do is suggesting sane values for data and settings.
This way it is easy to create scripts, packages, and any other provisioning method that are "compatible" between them.

Here is a list of things to decide upon:

  • fsdb directory
  • users db path
  • LIBREANT_SETTINGS
  • PRESET_PATHS
@boyska boyska added the docs label Nov 23, 2015
@boyska
Copy link
Member Author

boyska commented Nov 23, 2015

fsdb is hard for me to decide: by its nature, having a single /var/lib/fsdb to be used by multiple applications seems nice. However, this would make the removal of unreferenced files virtually impossible. So maybe /var/lib/libreant/fsdb/ is a better guess.

users db could just go in /var/lib/libreant/users.sqlite

LIBREANT_SETTING should be /etc/libreant.json. But since we might have other configuration files, /etc/libreant/libreant.json may be better

PRESET_PATHS should be /etc/libreant/presets/. If we want to have default presets, we might just ship them in /usr/share/libreant/default/presets/ and suggest the user to add that directory to PRESET_PATHS. If the distribution want to ship default presets, it might just put files under /etc/libreant/presets/ (similarly to apache2 configuration on debian, for example)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant