-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old wekan version in snapstore #5226
Comments
Yes. There will be automatic upgrade to newest. I'm In Progress of fixing related migration issues. |
No, that is incorrect. Candidate channel has newest WeKan: |
I also have installed version 6.09. When I try to update with these code
The newest version is installed now. Wekan is not available after updating. When I refresh to the stable version, wekan is available again. Updating to the newest version is not possible. Maybe you have an other way to update wekan to the candidate version... |
I'm currently coding automatic upgrade. It will upgrade all Snap Stable from 6.09 to newest WeKan automatically. Manual upgrade currently has too many steps, that are time too consuming to do manually:
3.2) Convert attachments database structure to new format, with upcoming code function:
I'm currently writing code functions for all that. I do not recommend trying it manually. |
These are my current In Progress scripts for upgrade and downgrade. These do not yet make attachments visible, coding that is In Progress. upgrade.sh
downgrade.sh
|
Nice to know. Thank you for your work. Do you have any suggestions when the script is done? The stable version will automatically upgrade to the newest version when the script is finished, right? |
For any code, it is so unpredictable how long it takes to finish it, I don't know. Most likely I will add that script to this issue, when I have finished it, to make possible manual upgrade. There is also other questions related to how to upgrade Caddy 1 to newest, when AFAIK Caddy 2 does not support Caddy 1 Caddyfile file format. |
One more question @xet7 . When I install the latest candidate on a new system, is the latest candidate version updated automaticly by snap? I think the problem is the old version updating to the newsest isn't it? |
Yes, Snap Candidate is updated automatically by Snap, it is always newest version. After I have fixed migrations, I will release newest WeKan also to Snap Stable. Those migrations will convert Snap Stable to newest WeKan, updating database, attachments etc. |
First of all, thank you for the support and the effort. |
any updates? |
The point is for you to wait, when I have fixed attachments migration code, and released automatic update, that updates Snap Stable from 6.09 to newest 7.x automatically. |
Hi @xet7 I just wanted to ask, if there is any update about this topic? thank you and best regards, |
I would like to migrate from MongoDB to SQLite, with: a) Meteor WeKan and FerretDB https://forums.meteor.com/t/ferretdb-1-18-now-has-oplog-support-trying-replace-mongodb-6-x-with-ferretdb-postgresql-or-ferretdb-sqlite/61092 b) WeKan Studio https://github.com/wekan/wekanstudio Just because of:
Alternative would be to try to migrate from MongoDB 3 to MongoDB 6, by fixing this code at Snap. But hurrying that would probably mean much more disk space required when migrating, out of disk space problems, and multiple migrations like MongoDB 3 to MongoDB 6 to SQLite. I would prefer only one migration, to SQLite. |
Thank you, what would that mean for the update? If I migrate to SQLite, how can I update the installed Wekan version? Best regards, |
No, you don't need to migrate anything. There will be automatic update to WeKan Snap Stable, that will upgrade from 6.09 to newest 7.x. |
Okay, thank you for the information. When the automatic update will be proceeded? Do I need to do anything? Thank you and best regards, |
No, you don't need to do anything. When I have finished additional code, and released it to Snap Stable, it updates all Snap Stable installs wordwide automatically very fast. There is no exact date when it will happen. It will be when fixes are ready and tested that they work. |
@xet7 : sooo..., no more MongoDB, next stable will be using SQLite? (great news, actually) |
Yes, that is the plan. |
Is there something I can do to help you? |
Yes. Send PRs related to any open issues. And tag me with @xet7 if some issue can be closed. These help every WeKan user. |
Should be fixed with this pull |
Hi! Best Regards, lezioul |
No, I think. At least it did not work for me, when I tried to change from Stable to Candidate. MongoDB had some error, related to raw database files of MongoDB 3 not being compatible with MongoDB 6. I presume it requires mongodump from MongoDB 3, and mongorestore to MongoDB 6. Maybe other changes too, if attachments are not visible. |
hi xet7, is there any way to help you manage a seamless transition from wekan stable to edge? Regards |
It would help for someone to test current migration scripts, do they work at all, and improve them, to migrate from MongoDB 3 to 6: https://github.com/wekan/wekan/blob/main/snap-src/bin/mongodb-control#L21 https://github.com/wekan/wekan/blob/main/snapcraft.yaml#L200 It's possible to build snap package with:
And then have WeKan Stable Snap 6.09, and try to install new snap, does it upgrade correctly:
|
Hello,
in the snapstore is only an "old" version of wekan available:
wekan 6.09 from Lauri Ojansivu (xet7) installed
Best regards,
Danny
The text was updated successfully, but these errors were encountered: