-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Regular new releases #3146
Comments
Hey @AmritasyaPutra, I think you should definitely switch to using the dev branch. I've been running known in production from this branch |
Thanks. I went to the dev branch and that works fine on PHP 8.1. I moved from 1.2.2+2020061101 to 1.3.1+2020120201. schema label has the value 2020120301 in versions table. Looking at function checkAndUpgradeSchema() this seems to be the latest schema. Now I am getting the following errors, what should I do: I don't have 'siteid' in my config, entities and reader tables and my site and site_metadata tables are empty. The site is 'appearing' alright, here it is : https://k.ekvastra.in/ doesn't this mean something was missed during schema upgrade? |
I ran the alter table statements in 2020111301.sql manually. That takes care of the missing columns. What should I run next before I can run update statements from 2020120201.sql? Inspecting the logs I see that only the following schema update was run, unfortunately I do not have the backup of the table before this ran to debug further: |
Hey! The mysql migration directory contains:
Since only 2020120201.sql might be missing, UPDATE `entities` set `siteid` = ( SELECT `_id` FROM `site` limit 1 );
UPDATE `reader` set `siteid` = ( SELECT `_id` FROM `site` limit 1 );
UPDATE `config` set `siteid` = ( SELECT `_id` FROM `site` limit 1 ); Those update queries won't hurt Please make a backup of your database before running migrations. |
Thanks. I agree... but since my site and site_metadata tables are empty the above update commands won't do anything. There must have been some code at some point that seeds the siteid in the site table it if it is empty. This appears to be a tolerable scenario... not having any siteid, because my site is working fine. |
We released Known 1.5 yesterday. From here on out you can expect incremental new releases at least every two months. |
Amazing! Congratulations on the release and |
Updating to say that, well, this didn't happen. I think one of the reasons is that the codebase has become overloaded and crufty. My suspicion is that we need to reduce dependencies, delete a lot of code, and return to a leaner architecture. Thinking about how this can be done well. I still depend on Known and I know others do too. |
I used known to migrate my old blog. I used a shared hosting and have 7 other web applications. I could upgrade everything to PHP 8.1 from PHP 7.4 with very little effort but with "Known" I am having a tough time because I need to update the dependency / vendor. This must be a common headache with many users. Having regular release not only solves this problem but also sends a positive message to the users about regular activity. This also means publishing well defined improvements and fixes done in a release. If there are no such defined steps in over 3 years it looks poor.
The text was updated successfully, but these errors were encountered: