item (@item@libera.site)
#Pleroma #Statistics 2024-05-03 21:00 CEST
Number of active instances: 1 406
Number of users: 151 429
Number of statuses: 37 301 650
Number of users last 4h: 11
Number of statuses last 4h: 9379
#Fediverse
Show Original Post
item (@item@libera.site)
#Pleroma #Statistics 2024-05-03 13:00 CEST
Number of active instances: 1 408
Number of users: 151 404
Number of statuses: 37 286 774
Number of users last 4h: 9
Number of statuses last 4h: 4174
#Fediverse
Show Original Post
objects (@objects@sironi.tk)
@rolle @snarfed.org@snarfed.org
as for #pleroma bugs, i'm not able to test :-(
is it correct that i just see a couple posts on your bsky bridged profile, without an account ?
https://bsky.app/profile/rolle.mementomori.social.ap.brid.gy
Show Original Post
objects (@objects@sironi.tk)
@snarfed.org@snarfed.org seems i can't follow / find
@bsky.brid.gy@bsky.brid.gy
from #pleroma :-(
cc
@lain
Show Original Post
objects (@objects@social.saria.fun)
Adventures in upgrading Pleroma 👩🏾‍💻
Just upgraded #Pleroma, which I’d been putting off for a while.
I had been using the packaged, “OTP”, version of Pleroma, but it turned out the package is ancient, and it required an older cryptography library. Because I’d upgraded to a newer version of #Ubuntu, the older crypto library had been removed and replaced with a newer version.
I found all this out when I tried to upgrade and got an error, searched for the error text, and found the bug report with a detailed explanation of the problem and solution.
So, I just backed up my instance, removed the OTP version of Pleroma, and re-installed it directly from the source repository.
The whole process took maybe half an hour, and no more than 10 or so commands. Basically:
- Stop Pleroma (so it’s not running while trying to backup/update):
sudo systemctl stop pleroma. - Backup my instance.
- First make a place to store the backup:
mkdir -p ~/backup/pleroma. I made it (temporarily!) world-writable to make things easier:chmod 777 ~/backup/pleroma. - Backup the database:
sudo -Hu postgres pg_dump -d pleroma --format=custom -f /home/saria/backup/pleroma/pleroma.pgdump. - Backup the configuration:
sudo cp /etc/pleroma/config.exs /home/saria/backup/pleroma.
- First make a place to store the backup:
- Delete the Pleroma installation (actually, just put it to one side for now, just in case):
sudo mv /opt/pleroma /home/saria/backup/pleroma/old-installationandsudo mv /etc/pleroma /home/saria/backup/pleroma/old-configuration. - Adjust stuff that differs between the OTP installation and the source installation.
- Update the pleroma user’s home directory:
sudo usermod -d /var/lib/pleroma pleroma(Here I got an error that the pleroma user was still running process 758. No problem, justsudo kill 758, then retry.) - Make the “new” locations:
sudo mkdir - /opt/pleroma /var/lib/pleroma. (I think/var/lib/pleromaalready existed, and was storing images and uploads, which was fine.) - Make the pleroma user the owner of those locations:
sudo chown -R pleroma: /opt/pleroma /var/lib/pleroma.
- Update the pleroma user’s home directory:
- Change to the pleroma direcory:
cd /opt/pleroma. - Download pleroma:
sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma. - Build pleroma.
- Get the dependencies:
sudo -Hu pleroma mix deps.get. - Run the build:
sudo -Hu pleroma MIX_ENV=prod mix pleroma.instance gen.
- Get the dependencies:
- Configure pleroma.
- Copy the generated configuration file:
sudo -Hu pleroma mv config/generated_config.exs config/prod.secret.exs. - Edit the configuration file
config/prod.secret.exs, copying all the important stuff (passwords, salts, personal settings) from the old file at/home/saria/backup/pleroma/old-configuration/config.exs.
- Copy the generated configuration file:
- Run the database migration:
sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate. - Restart Pleroma:
sudo systemctl start pleroma. I discovered (usingsudo systemctl status pleroma) that Pleroma would not start. I realised that was because the systemd service file was still trying to start the old, OTP version. So I replaced the service file with the one from the source installation (sudo cp -f /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service) and tried again. Now I got an error from systemd because the service file had changed, telling me I had to dosystemd daemon-reload. So I didsudo systemd daemon-reload, and tried to start Pleroma again. Success! 🦸🏾‍♀️
As you can see, I ran into some hiccups, but the documentation and error messages were clear enough that I was able to fix stuff and move on.
Now, I am no expert on any of this stuff! I know literally nothing about Erlang or Elixir (the languages/tools/whatever that Pleroma is made with). But as you can see, if you take the time to carefully read the documentation, and understand what each step is actually doing, it’s really not that hard! 💪🏾
Show Original Post
objects (@objects@social.fedcast.ch)
@cob Ich habe eigene #Pleroma und #Hubzilla Instanzen installiert. WĂĽsste nicht, das dies nicht funktionieren sollte... oder man mĂĽsste dieses Beispiel genauer analysieren - zB. Reichweiten-Einstellung etc.
@crossgolf_rebel @MediaOnMastodon
Show Original Post
0xDEADBEEF (@0xDEADBEEF@fosstodon.org)
@bitzero
#pleroma FTW.
What's the drama with mastodon?
Show Original Post
PanzerKern (@PanzerKern@tech.lgbt)
Wondering if someone could point me to any info on the topic of Akkoma's/Pleroma's "database issues?" I hear it mentioned as one of the downsides to running it as an instance that causes issues over time, but it's always vague.
The best I can gather is the schema sucks, but I'd like to know details on which parts are bad and why.
Show Original Post
coloco (@coloco@mstdn.social)
Hide muted #threads in #pleroma
https://pleroma.p4g.club/users/coloco
Show Original Post
item (@item@libera.site)
#Pleroma #Statistics 2024-04-28 17:00 CEST
Number of active instances: 1 404
Number of users: 155 942
Number of statuses: 37 195 601
Number of users last 4h: 69
Number of statuses last 4h: 8384
#Fediverse
Show Original Post