Untitled attachment

Notices where this attachment appears

1. Embed this notice
    (mint@ryona.agency)'s status on Sunday, 07-Jul-2024 02:07:49 JST 

   in reply to
   @Cocoa @p Alright, tested the process out on a VM with rebased that has like one user and three posts. I'm gonna assume you followed instructions on https://soapbox.pub/install/ during initial installation (which for whatever reason make you use some third-party package manager for Erlang/Elixir, which I think should work with base Pleroma). If not, you should already know whether something should be adjusted.
   1. Stop pleromer (`systemctl stop pleroma` or whatever other init system you use)
   2. Log in as pleroma user (`sudo -Hu pleroma bash`) and enter /opt/pleroma
   3. Rollback vegan-specific migrations by executing following commands in that order:
   MIX_ENV=prod mix pleroma.database rollback 20221207235104
   MIX_ENV=prod mix pleroma.database rollback 20221029171353
   MIX_ENV=prod mix pleroma.database rollback 20220927220033
   MIX_ENV=prod mix pleroma.database rollback 20220819171321
   MIX_ENV=prod mix pleroma.database rollback 20220624104914
   MIX_ENV=prod mix pleroma.database rollback 20220225164000
   MIX_ENV=prod mix pleroma.database rollback 20210612185407
   4. Exit pleroma user (`exit`) and drop the column that can't be rolled back with mix: `sudo -Hu postgres psql pleroma -c "alter table users drop column location;"`
   5. Go back to /opt, rename /opt/pleroma into something else (e.g. `mv /opt/pleroma /opt/glussy`), then clone upstream repo (`git clone https://git.pleroma.social/pleroma/pleroma`)
   6. Copy config/prod.secret.exs from old directory to new.
   7. Log back in as pleroma user, go to /opt/pleroma and run the following to compile the new version and migrate the DB
   mix local.hex --force
   mix local.rebar --force
   mix deps.get
   MIX_ENV=prod mix compile
   MIX_ENV=prod mix ecto.migrate
   8. After all that's done, log out and restart pleromer (`systemctl start pleroma`). If there are no invalid config entries, it should work out of box. If not, stop pleromer and try running it manually (`sudo -Hu pleroma MIX_ENV=prod mix phx.server`) then tell me what the error is. Worst case scenario, you'd have to remove DB configs (`TRUNCATE TABLE config`) and reconfigure it manually.
2. Embed this notice
   Mr. Bacon (tony@clew.lol)'s status on Saturday, 30-Mar-2024 14:12:51 JST Mr. Bacon

   in reply to
   It's in grafs pinnned posts. It's what i used. It walks you through about everything you might need.
   
   https://soapbox.pub/install/
3. Embed this notice
   Mr. Bacon (tony@clew.lol)'s status on Monday, 18-Dec-2023 13:34:12 JST Mr. Bacon

   in reply to
   https://soapbox.pub/install/
   
   has a good walk through (by alex gleason) it walks you through how to download and set up your own instance.
   
   This plus chat gpt for asking questions is was got me by
   
   I use hetzner as a vps. costs like $3/month
   
   If you don't like soapbox, that's fine, but the set up process should be similar.
4. Embed this notice
   msilvya (msilvya@gleasonator.com)'s status on Friday, 15-Dec-2023 11:27:47 JST msilvya

   in reply to

   @alex @olmitch Alex - So, run the usual steps from https://soapbox.pub/install/ ?

   sudo -Hu pleroma bash cd /opt/pleroma git pull origin develop asdf install mix deps.get MIX_ENV=prod mix ecto.migrate exit systemctl restart pleroma
5. Embed this notice
   Matty (matty@nicecrew.digital)'s status on Thursday, 14-Dec-2023 05:33:58 JST Matty

   in reply to
   dude what in the fuck did you follow the steps at https://soapbox.pub/install ?
6. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 04-Oct-2023 21:28:59 JST Alex Gleason
   @collappsar https://soapbox.pub/install
   
   Linode is fine. You want like 4GB RAM and 4CPUs minimum. But the bigger the better. It will get utilized.