GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    snacks (snacks@netzsphaere.xyz)'s status on Sunday, 02-Feb-2025 01:43:38 JST snacks snacks
    Has anyone set up pleroma/akkoma with backblaze b2?
    In conversation about 4 months ago from netzsphaere.xyz permalink
    • Embed this notice
      snacks (snacks@netzsphaere.xyz)'s status on Sunday, 02-Feb-2025 01:52:10 JST snacks snacks
      in reply to
      like, i'm starting to think b2 just doesn't work at all
      In conversation about 4 months ago permalink
    • Embed this notice
      snacks (snacks@netzsphaere.xyz)'s status on Sunday, 02-Feb-2025 01:54:19 JST snacks snacks
      in reply to
      • meso [netzsphaere era]
      @meso yes, the s3 api doesn't work for some reason. you prob just fucked up your fe
      In conversation about 4 months ago permalink
    • Embed this notice
      meso [netzsphaere era] (meso@netzsphaere.xyz)'s status on Sunday, 02-Feb-2025 01:54:21 JST meso [netzsphaere era] meso [netzsphaere era]
      in reply to
      @snacks >go on asbestos
      >errors out or takes 10 minutes to upload my faggot shit
      >go on netzsphaere
      >doesnt even give me an error and refuses to upload
      In conversation about 4 months ago permalink
    • Embed this notice
      snacks (snacks@netzsphaere.xyz)'s status on Sunday, 02-Feb-2025 01:54:35 JST snacks snacks
      in reply to
      • meso [netzsphaere era]
      @meso try reloading the page
      In conversation about 4 months ago permalink
    • Embed this notice
      kaia (kaia@brotka.st)'s status on Sunday, 02-Feb-2025 05:27:42 JST kaia kaia
      in reply to
      @snacks we only use it for backup, not for media, and it works okie.
      In conversation about 4 months ago permalink
      snacks likes this.
    • Embed this notice
      snacks (snacks@netzsphaere.xyz)'s status on Sunday, 02-Feb-2025 05:28:42 JST snacks snacks
      in reply to
      • kaia
      @kaia what program do you use? s3cmd has issues with backblaze it seems
      In conversation about 4 months ago permalink
    • Embed this notice
      kaia (kaia@brotka.st)'s status on Sunday, 02-Feb-2025 05:31:50 JST kaia kaia
      in reply to

      @snacks the b2 command

      #!/bin/bash BACKUP_DIR="/opt/akkoma/backup" BUCKET_NAME="brotkastbackup" DATE=$(date +%Y%m%d) BACKUP_FILE="$DATE-akkoma.pgdump" ENCRYPTED_FILE="${BACKUP_FILE}.enc" SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )" export B2_APPLICATION_KEY_ID="" export B2_APPLICATION_KEY="" # Your encryption key - store this securely! ENCRYPTION_KEY="" # Stop docker compose docker compose stop docker compose up db -d # Create backup docker compose exec db pg_dump -d akkoma --format=custom -f ./backup/$BACKUP_FILE # Start docker compose again docker compose up akkoma -d # Encrypt the backup openssl enc -aes-256-cbc -salt -in "$BACKUP_DIR/$BACKUP_FILE" -out "$BACKUP_DIR/$ENCRYPTED_FILE" -k "$ENCRYPTION_KEY" -pbkdf2 # Upload encrypted file to B2 if $SCRIPT_DIR/venv/bin/b2 file upload $BUCKET_NAME "$BACKUP_DIR/$ENCRYPTED_FILE" "backups/$ENCRYPTED_FILE"; then # Delete local files only if upload was successful # rm "$BACKUP_DIR/$BACKUP_FILE" "$BACKUP_DIR/$ENCRYPTED_FILE" echo "Backup completed, encrypted, and uploaded successfully" else echo "Upload failed - keeping local backup files" exit 1 fi
      In conversation about 4 months ago permalink
      snacks likes this.
    • Embed this notice
      Phantasm (phnt@fluffytail.org)'s status on Monday, 03-Feb-2025 06:26:00 JST Phantasm Phantasm
      in reply to
      • kaia

      @kaia @snacks

      docker compose exec db pg_dump -d akkoma --format=custom -f ./backup/$BACKUP_FILE

      If I remember correctly, you had some problems with long restore times for the Akkoma DB when you were moving away from Contabo. This line is the source of the problem. The custom format has issues with some indexes and by default does not disable triggers when restoring, which makes PostgreSQL do a lot of unneeded work. Disabling triggers might work with the custom format, but I never tested it properly.

      This is what currently use on PostgreSQL 12:

      === schema === sudo -Hu postgres pg_dump -s pleroma -S postgres -v -f /mnt/backup/pleroma-schema.psql === data === pg_dump -a pleroma --disable-triggers -S postgres -v -f - | nice bzip2 -z9 - >/mnt/backup/pleroma-data.psql.bz2 (must be ran as the postgres user, due to write permission for backup directory)

      Restoration is then done with psql instead of pg_restore.

      In conversation about 4 months ago permalink
      kaia and snacks like this.
    • Embed this notice
      kaia (kaia@brotka.st)'s status on Monday, 03-Feb-2025 07:00:18 JST kaia kaia
      in reply to
      • Phantasm
      @phnt @snacks
      thank you, bookmarking
      In conversation about 4 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.