[–] 1 point 3 months ago (1 child)

Hello!

Its been just about a year since someone forwarded this post to me, and I just want to say, I ABSOLUTELY LOVE COPYPARTY

I've kinda started using it for everything. It may have gotten out-of-hand...

A short list:

  • I use it as the primary file sharing server for a small community I help run
  • I use it as a personal file storage system with search (I wrote a custom plug-in for it that adds content-based search via meilisearch)
  • Perhaps most-unhinged, I started using it the primary network-based file system on my LAN. It has so many more useful features for this than NFS, SSHFS, and Samba that it just became the obvious choice. I set up a webDAV share with a username/password and then mount it via systemd-mount and rclone, and its been working shockingly well.

Thank you so much for making copyparty, and thank you for posting this <3

  • source
  • [–] [S] 2 points 1 year ago

    I am very happy to hear that. Sadly I don't know what to do about the images not loading. I am just using the free tier of pico.sh, so I imagine that corners have been cut for pathological consumers like me. If you ever need a specific image or something doesn't make sense, feel free to DM!

  • source
  • parent
  • context
  • [–] [S] 4 points 1 year ago

    Yeah a little xD but FWIW this article series is based on what I personally run (and have set up for several friends) and its been doing pretty well for at least a year.

    But I have backups which can be used to recover from the issues with breaking updates.

  • source
  • parent
  • context
  • [–] [S] 8 points 1 year ago (2 children)

    I don't disagree with any of that, I'm merely making a different value judgement - namely that a breach that could've been prevented by automatic updates is worse than an outage caused by the same.

    I will however make this choice more explicit in the articles and outline the risks.

  • source
  • parent
  • context
  • [–] [S] 8 points 1 year ago (10 children)

    That's reasonable, however, my personal bias is towards security and I feel like if I don't push people towards automated updates, they will leave vulnerable, un-updated containers exposed to the web. I think a better approach would be to push for backups with versioning. I forgot to add that I am planning a "backups with Syncthing" article as well, I will take this into consideration, add it to the article, and use it as a way to demonstrate recovery in the event of such an issue.

  • source
  • parent
  • context
  •  

    Recently, I've found myself walking several friends through what is essentially the same basic setup:

    • Install Ubuntu server
    • Install Docker
    • Configure Tailscale
    • Configure Dockge
    • Set up automatic updates on Ubuntu/Apt and Dockge/Docker
    • Self-host a few web apps, some publicly available, some on the Tailnet.

    After realizing that this setup is generally pretty good for relative newcomers to self-hosting and is pretty stable (in the sense that it runs for a while and remains up-to-date without much human interference) I decided that I should write a few blog posts about how it works so that other people can set it up for themselves.

    As of right now, there's:

    Coming soon:

    • Immich
    • Backups with Syncthing
    • Jellyfin
    • Elementary monitoring with Homepage
    • Cloudflare Tunnels

    Constructive feedback is always appreciated.

    EDIT: Forgot to mention that I am planning a backups article