Vikunja update strategy
-
Hi. I'd like to request to:
- either update Vikunja based on the latest "unstable" version, or
- provide a separate Package that follows the "unstable" versions.
Because, the maintainers of this tool don't seem to favour stable releases. Instead, they focus primarily on "unstable" releases, even using those versions for their cloud offering.
-
J james marked this topic as a regular topic
-
Hello @shrey
I am relaying this topic internally for discussion.In the meanwhile, how comfortable are you changing the app yourself?
-
Hello @shrey
Since the app is already packaged the majority of work is already done.What you need:
- docker and a dockerhub account
- the cloudron cli
- git
Step 1 - clone the original repo or better fork it
Source Repo: https://git.cloudron.io/packages/vikunja-app
In this repo edit the
Dockerfileand change the version to your desired version, the line in question is:ARG VIKUNJA_VERSION=0.24.6Save and close the file.
Now you can edit the
CloudronManifest.jsonand bump the versions:this is the cloudron app version
"version": "1.17.3"and this is the upstream version which should reflect the version in the Dockerfile
"upstreamVersion": "0.24.6"Save and close.
Now you need to build the image:
# Don't miss the . at the end of this line docker build -t YOUR_DOCKERHUB_USERNAME/io.vikunja.cloudronapp:1.17.3 .Push the image:
docker push YOUR_DOCKERHUB_USERNAME/io.vikunja.cloudronapp:1.17.3Now you could install your custom image to your cloudron.
cloudron login my.DOMAIN.TLD cloudron install --location CustomVikunja --image YOUR_DOCKERHUB_USERNAME/io.vikunja.cloudronapp:1.17.3
if you wish to update your already installed vikunja, create a clone from your latest backup and update that one first to insure everything is working!cloudron update --app CustomVikunja --image YOUR_DOCKERHUB_USERNAME/io.vikunja.cloudronapp:1.17.3 -
@james Thanks for explaining how to package how own version, that's really good to know in general!
@shrey Just to say, I don't think the dev doesn't favour stable versions. Most versions are stable on the repo, it's just that there is major update coming (v1.0) and so they've released a few RC before release it stable, but that's pretty standard practice.