Problem
Currently, when deploying OpenTogetherTube, the user must manually edit the text config found in env/, usually env/production.env, to add various API keys. This works fine, but may not be suitable for people that aren't very technically inclined.
Solution
On first run, a URL should be provided to guide the user through creating an administrator account, adding API keys, and setting other options.
After setup, the administrator account should still have access to modify the config through a web interface.
Describe alternatives you've considered
The current way to configure OpenTogetherTube is adequate, but not exactly ideal when deploying in a docker container.
Additional context
N/A
Problem
Currently, when deploying OpenTogetherTube, the user must manually edit the text config found in
env/, usuallyenv/production.env, to add various API keys. This works fine, but may not be suitable for people that aren't very technically inclined.Solution
On first run, a URL should be provided to guide the user through creating an administrator account, adding API keys, and setting other options.
After setup, the administrator account should still have access to modify the config through a web interface.
Describe alternatives you've considered
The current way to configure OpenTogetherTube is adequate, but not exactly ideal when deploying in a docker container.
Additional context
N/A