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

Initial configuration capability #64

Open
Libbum opened this issue Nov 29, 2017 · 1 comment
Open

Initial configuration capability #64

Libbum opened this issue Nov 29, 2017 · 1 comment

Comments

@Libbum
Copy link
Owner

Libbum commented Nov 29, 2017

Currently we set up things like the notification system (#62) in plain text in the config file. It would be better if some of this info was stored in the database encrypted.

Clap can enable sub-commands, wherein we can run a CLI module to enter in username/password details directly for example.

Consideration on whether this is needed if we have a running Admin backend (#16) should also be investigated.

@Libbum
Copy link
Owner Author

Libbum commented Nov 29, 2017

Another thought:
Users will not necessarily need to use the development tools to use Oration once #57 is sorted, so the requirement to run the diesel migrations should be folded into this setup process.

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