~tsileo/microblog.pub#91: 
Support configuration via env variables

Hey there! Wonderful project you got here!

While testing it before running it on my server I realized I’d need to first configure it from the command line.

That is sometimes not very “ergonomic” , for example in systems like unRAID, where Docker containers are managed with a GUI. I suppose the same might be true for Portainer or Docker Desktop.

May I propose that if the data volume has not been started and the config options are passed as env variables everything be auto generated?

The user could then go ahead and edit the generated data files should they want to.

Thanks for considering it and thanks for a great piece of software!

-Saúl

Status
REPORTED
Submitter
Saúl Ibarra Corretgé
Assigned to
No-one
Submitted
a month ago
Updated
a month ago
Labels
No labels applied.

~tsileo a month ago

Hey, thank you.

I will give it more thoughts and get back to you here.

I don't think this is a high-priority issue, but improving the setup would be nice.

I do think requiring the CLI is ok, and that alternative way to setup may not be necessarily baked into this repo. For example, the YunoHost installer allows to do the initial setup via a web UI.

Thanks!

Saúl Ibarra Corretgé a month ago · edit

Thanks for keeping an open mind :-)

I’ll check how you did the YuNoHost setup, maybe I can borrow some inspiration.

-Saúl

On 23 Dec 2022, at 09:49, ~tsileo outgoing@sr.ht wrote:

Hey, thank you.

I will give it more thoughts and get back to you here.

I don't think this is a high-priority issue, but improving the setup would be nice.

I do think requiring the CLI is ok, and that alternative way to setup may not be necessarily baked into this repo. For example, the YunoHost installer allows to do the initial setup via a web UI.

Thanks!

-- View on the web: https://todo.sr.ht/~tsileo/microblog.pub/91#event-218440

Register here or Log in to comment, or comment via email.