Filtered word: nsfw
Hi there,
the moment has come to do the first instance upgrade cycle in the life of this instalation to bring this server to the actual stable version 2024.12-1 in the comming days.
In part the idea is to document every step in a post similiar to the howTo instructions:
install and/or move friendica to ubuntu 22.04 LTS VPS server
in the @EDIT | don't follow! profile.
Right now we are on 2023.05, so we will have to update step by step to:
2023.12 | release notes
2024.03 | release notes
2024.08 | release notes
2024.12-1 | release notes
Are there any specific recomandations or details to have in mind besides the information expected to be found in every update release instruction?
This is basically a single user instance with round about 14 forum pages with few followers each and a total of 18 profiles with contacts in the activityPub and diaspora community and some RSS subscriptions. No other specific conectors are enabled.
Installed addons/apps:
blockbot, calc, impressum, js_upload, notifyall, nsfw, pageheader, phpmailer, qcomment, rendertime, showmore_dyn, startpage
DB backups amount to ~180MiB and the image file storage folder on ftp around ~400MiB.
Friendica stable | 'Giant Rhubarb' 2023.05 - 1518
PHP Version 8.1.2-1ubuntu2.14
VPS server | Ubuntu 22.04 LTS
4 Core CPU, 8 GB Ram with 300GB NVME Disk - unlimited traffic
hosted by @ raroun 👍
Notes:
This instances right now seems to work well.
Sometimes this profile here has some strange hickups like when following up the link of a post from this server in a stream view a message "Not Found |The requested item doesn't exist or has been deleted." Also right now profiles from contacts, for example @ hoergen or @ feb don't show up in the contact list but they are displayed as followed in the profile contact page.
TupambAdminOrg [2024.03]
•added the respective links to the publication.
I guess there is nothing to add with respect to the difference between 2024.12 and 12-1, it's just installing 2024.12-1 instead of 2024.12 (?).
TupambAdminOrg [2024.03]
•¿from github?
On github it looks like 12-1 was released a day later (right now it states 29 days) than 12 (1 month), as if it is a fix, also it states:
In the list of tags it looks like "older" or lesser in the hierarchy.
[as of now just edited the difference in the inicial post between github branch and anouncement post]
utopiArte
•Learning/comprehension question @Tobias:
What does "in Friendica" mean?
The stable version 2024.12, in other words the github pull of 2024.12 even when the date says "1 month" like it if werent as upt o date than 12-1?
TupambAdminOrg [2024.03]
•In other words @Tobias, these are changes in files on github for github and are not transfered by a git pull, right?
(a like for verifying refrasing questions to asure that I got the comment right is suffice @ Tobi!)
utopiArte
•I understand that it's not relevant because it's an "auxiliar file".
👍
At the same time I do have to point out that you did two opposite staments, didn't you?
🤔
…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup
•Starting this announced updating cycle now.
Question:
Release notes and news forum announcement do not mention setting the site into maintenance mode by "going offline" stopping cron job:
and the following command:
This is described for moving from one server to another in the helpers page:
https://forum.friendi.ca/help/Migrate
Shouldn't this be somehow be a more safe procedure?
Planning to do that right now ..
…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup
•Problems using github update.
Trying to pull the update from 2023.05 to 2023.12 I get the message that the branch I'm trying to pull doesn't exist:
www-data@myservername:~/html$ git pull https://github.com/friendica/friendica/tree/2023.12
fatal: repository 'https://github.com/friendica/friendica/tree/2023.12/' not found
What am I doing wrong?
…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup
•TupambAdminOrg [2024.03]
•Database structure update 1542 was successfully applied.

👍
TupambAdminOrg [2024.03]
•Serializer.php php line 298
2025-02-20T22:15:46Z WARNING app E_USER_WARNING: Directory /var/www/html/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer not writable.Directory /var/www/html/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer not writable.
file
/var/www/html/vendor/ezyang/htmlpurifier/library/HTMLPurifier/DefinitionCache/Serializer.php
php line 298
error 512
Hypolite Petovan
•/vendor
unable to modify by the web server user.Friendica Support reshared this.
utopiArte
•hypolite wrote:
vendor ownership
drwxr-xr-x 40 www-data www-data 4096 Feb 20 21:22 vendor
drwxr-xr-x 3 www-data www-data 4096 Feb 20 21:20 ezyang
drwxr-xr-x 3 root root 4096 Feb 20 21:20 htmlpurifier
hypolite wrote:
vendor ownership
drwxr-xr-x 40 www-data www-data 4096 Feb 20 21:22 vendor
drwxr-xr-x 3 www-data www-data 4096 Feb 20 21:20 ezyang
drwxr-xr-x 3 root root 4096 Feb 20 21:20 htmlpurifier
There has been problems before with nearly all folders becoming owned by root.
In this upgrade I made the mistake to initialize
bin/composer.phar install --no-dev
as root but aborted that intent, changed to www-data and appliedbin/composer.phar install --no-dev
again.Command applied now to asure that all folders will be owned by www-data.
chown -R www-data:www-data /var/www/
Hypolite Petovan likes this.
utopiArte
•Ownership, www-data and root related conversation from last year when the instalation was migrated to this VPS:
https://tupambae.org/display/0ac89072-1765-64c7-8419-cd5442334821
utopiArte
2023-11-27 16:44:52
Ownership, www-data and root related conversation from last year when the instalation was migrated to this VPS:
https://tupambae.org/display/0ac89072-1765-64c7-8419-cd5442334821
utopiArte
2023-11-27 16:44:52
utopiArte
•2023.12 felt faster than 2023.05.
utopiArte
•TupambAdminOrg [2024.03]
•👍