For anyone else out there who has Vikunja deployed using docker, please take note that the vikunja/api and vikunja/frontend containers have been combined into a single vikunja/vikunja container as part of release 0.23. You will have to update your compose files to reflect this change as part of the upgrade. I just went through this and it went very smoothly. The directions on the linked webpage make it fairly easy. Happy self-hosting!
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Man I have been looking for something like this with Gantt charts. Thank you so much.
They are liars.
There are THREE South American camelids: llamas, vicuñas, and guanacos. 😤
Misleading title… Vikunja doesn’t require docker compose. You can run it other ways. I’m running it on k8s.
deleted by creator
What is your purpose?