Environmental Variables #1746
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1746
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've stumbled across this app and I think it's going to be able to meet my needs and see me move across from Todoist. Wooo!
However, I think I'm hit a stumbling block and I hope someone can help.
I'm running this on an RPi (w/docker) and I have the front/back end operating fine with the default setup - database is locally hosted, not mariadb.
I can't figure out for the life of me how to set & where to place the variables mentioned here: https://vikunja.io/docs/config-options/
Thanks in advance :)
Hey there, glad you like Vikunja!
If you're running Vikunja with docker, I would reccomend using docker-compose. In docker-compose you can set the environment variables as usual at the
environment
property. You can see this in the docker examples.What does your setup look like?
The thing is, I can't work out how to translate
enableregistration
: true to an env variable for the docker-compose.I've tried adding it to both front & rear end via portainer and nothing happens. I suspect I'm doing something wrong?
I should add the the below works except the environmental variables.
Here's my setup.
The
enableregistration
key is located under theservice
key which translates toVIKUNJA_SERVICE_ENABLEREGISTRATION
for the env variable. That's the same system for all of the config variables.I think that's what I need :)
Brain wasn't functioning. Problem is I know enough to be dangerous (w/docker) but not enough to get myself out of a pickle...
Thank You!
In case anyone is wondering in the future: