• 2 Posts
  • 38 Comments
Joined 3 years ago
cake
Cake day: July 10th, 2023

help-circle



  • Stow/chezmoi/your choice for dotfiles, config mgmt for system config. You don’t need to rebuild whole server to start with ansible tho, you can take over one file at a time and grow as you learn.

    As you’ve found I don’t know of a tool that will cover both usecases as config mgmt for dotfiles is too much and dotfile mgrs for system config is probably out of their scope.








  • Sorry re-reading my comments it’s not super clear what I meant: nowhere else in the table do they take account for the ‘hidden’ on-going maintenance of looking after a server/self-hosting. So this is the only row where they address ‘cost’ and I just thought it’s a bit optimistic to say replacing all of Spotify just costs a one time server setup and storage. I think you’re saying this row was only meant to indicate financial cost and I agree it’s basically accurate from that meaning. However this is only the ‘initial’ cost. For example a self-hosted server and storage will eventually have to be replaced whereas Spotify will just keep replacing their own servers and that’s already baked into the price of your subscription (caveat: that Spotify price will rise over time).

    It’s not a big point really, maybe I’m nitpicking.










  • Thought process is: Peertube or some other service’s first job is the purpose for the service, so security likely won’t be as good as a service who’s first job is security.

    Really good point. I see many selfhost instructions now that say ‘we don’t bother with HTTPS, just use a proxy to handle that’ and maybe auth should go the same way as in there’s good solutions that specialise in auth so it’s not worth each project doing it themselves.

    apps can’t deal with hitting Authentik 1st afaik

    Another good consideration. There is an early Peertube app but I doubt my users will be using it, web access is fine for this. Perhaps apps for things like Lemmy/Mastodon/Peertube etc will need to work better with these auth frontends in future.