Config File

[davidnewhall]

The number of switches seems highly verbose. Are you interested in using a config file? I'd like to write some new features into this app, but I'd like to control some of it with run-time configuration. I'm not personally a huge fan of more than a couple CLI args. I usually have an arg for --config=/file/path and load the rest of my data from there. The items in the config file also unmarshal from env variables (using cnfg).

If I produce a changeset to move most of the CLI flags into a config file, are you open to that?

[davidnewhall]

To be clear, I'm kind of at a point where I'm not sure if I should fork the app and implement changes I need, or if you'd like to accept my contributions as I build out new features. I'd really like to start with some sort of configuration file so we can turn features on and off without flags. I see #13 and think that perhaps we can expose the configuration items to a UI and allow the app to update its own config as admins change things. Starting with the file seems ideal.

Features I need:

• no public pastes, no archive history, just unlisted, and private for logged-in users.
• enforced expiration (max 1 month in my case).
• auth provider control. auth providers without configuration should not be presented in the template.
• additional auth provider support. I want to add Discord oauth.
• less important, but on my todo list: client-side encryption using javascript. A compatible implementation in Go, so my other apps can POST encrypted data that I can decrypt with javascript.
• A solid API implementation with API Key support.
  • A way to add users externally with API keys.