• 1 Post
  • 20 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • You got quite good answers already, here and in the other thread.

    My suggestion is to not start with pixelfed but something else (simple stuff like dokuwiki, you can use it to document your stuff while you’re at it) to get an understanding of the whole process (running the service itself, making it available to the internet after hardening your infrastructure a bit etc).

    Also, if you’re not settled for how to do it exactly, give Docker a try. There’s a reason it’s popular among selfhosters!


  • Most important: replace the raspi SD card with an SSD

    General hardware: see if I find a better solution than my current Proxmox box (repurposed desktop which consumes 60w idling but is capped to 16GB Ram)

    Incoming traffic: currently having a VM that runs nothing but nginx and certbot. Considering switching to another reverse proxy and, more important, get proper monitoring of the logs (e.g. IP detection, 403, etc)

    Maybe add some iam like authentik

    Finding a solution for selfhosting podcasts client with sync on Android and Linux… gpodder never really seemed to work, considering audiobookshelf.

    Probably setting up calibre web and gethomepage

    Keeping what I have and maybe optimize a bit:

    • Prometheus stack
    • plenty exporters
    • Nextcloud
    • paperless
    • home assistant, mosquitto
    • pihole
    • vaultwarden
    • selfoss

    On VPS:

    • Mastodon
    • Bookwyrm
    • some WordPress (want to move this to my homeserver as well)











  • The resources required by federating depend on how many people follow each other across those two instances and how much these post. Just existing and theoretically federating doesn’t need any resources if there’s nobody following, assuming threads isn’t doing that different from everyone else.

    For each post a user makes on your instance, it sends that post to each instance where someone follows the poster. There’s no automatic sending to every known instance of every post on your instance.