Closed anmol26s closed 2 years ago
!testme
!testme
!testme
!testme
Migration from sqlite to mysql is not managed
Sqlite is now not supported by app. I don't know how to migrate from sqlite to mysql. Even if we do it I don't know if that would work. Maybe @kevinpapst can elaborate on, how to migrate existing Sqlite database to Mysql.
Why doing a partial switch of source to git ? Doing that we don't know which Kimai2 version will be installed ...
It's only for new installations. I don't know if its good idea to bring everyone to git.If you recommend we can try to move everyone to git. I did not do it because I don't have live running Kimai2 app. So there is no way to test that this would not break anything in while we migrate to git. We can always check the git tag to test the version of installed app. We can give option to use git or not to use it, while installation if installing with git is not OK with you.
There is a Ruby script which works: https://www.kimai.org/blog/2021/sqlite-and-ftp-support-removed/ But I would rather disallow migration from SQLite and show an explanation - doing the migration automatically would be great but feels a bit risky.
That would be lot of work and extra effort to migrate from Sql to Mysql. I don't know if its worth to make that much changes. So,
We can have a poll on Yuno to see if there are potential users that needs to migrated to Mysql.
Why doing a partial switch of source to git ? Doing that we don't know which Kimai2 version will be installed ...
It's only for new installations. I don't know if its good idea to bring everyone to git.If you recommend we can try to move everyone to git. I did not do it because I don't have live running Kimai2 app. So there is no way to test that this would not break anything in while we migrate to git. We can always check the git tag to test the version of installed app. We can give option to use git or not to use it, while installation if installing with git is not OK with you.
If you think that moving everyone to git is not a good idea, better to let all with app.src. But having to maintain two different source system will be difficult The point is there two options for me:
As being "the upstream" 😁 I can tell that the only requirements that changed in the last 1,5 years was:
As being "the upstream" 😁 I can tell that the only requirements that changed in the last 1,5 years was:
* the drop of SQLITE (which was always announced as being for test only, not production - my mistake that I didn't see it here earlier) * the change of minimum PHP version (being 7.2.9 now and the next version bumps it to PHP 7.3). So rather conservative as 7.2 support ended half a year ago and I guess YunoHost is more up-to-date?
It was a more general comment, not relative to Kimai ^^ because @anmol26s made several PR on several apps to switch them to git...
And Yes YunoHost PHP version is 7.3
And the question is: Do we prefer to have some packages to be late from the upstream app or do we prefer some of them having installation fail suddenly...
Ok, I silence myself 😁 this sounds like a general question that needs to be answered somewhere else.
Ok, I silence myself 😁 this sounds like a general question that needs to be answered somewhere else.
Sorry, it was in Kimai upgrade but I made a more general statement ^^
Git: Its more easy to change ecosystems.
Cons: each new installation can install an unknown new version, with new unmet requirements... Install may fail...
We can still use tags to force the package to stay on a particular version.
Git: Its more easy to change ecosystems.
Cons: each new installation can install an unknown new version, with new unmet requirements... Install may fail...
We can still use tags to force the package to stay on a particular version.
Good point using tags to specify the version to install and having previous app.src install moving to git source + manage the end of sqlite ^^
!testme
Do we need to migrate the sqlite to mysql? I think its better to give an error message and stop the upgrade if the instance is on sqlite.
Ok, no more option to force update. @yalh76
!testme
!testme
Problem
Solution