Now that more and more people are living as digital nomads, I just want a git server with S3 backend support so I can host it in the cloud.
I want to self-host, but I also don't want any infrastructure.
I want to self-host, but I also don't want any infrastructure.
I think I understand what you're saying, but to me, "self host" means you are running your own servers. I.e. managing your infrastructure.
Maybe there needs to be some other term for "using the cloud, but only as dumb storage." Like cloud _storage_ vs cloud _app_...
So this guy wants to run the software themself (the "self-host") without the infrastructure (the VPS which they rent yearly and which they have had to install Debian or Unbuntu 22, along with git and all the other software) - AWS replaces the infrastructure, and while it is close being "the cloud" it is still different because setting it all is still up to the user. They are still in control of their own data (although I guess some rogue AWS employee could read the data).
But then on the other hand I'm on the "that's not self-hosting!" side when you shift from your own needs to selling a service: if you run and sell a gitsomething.com and it's all on AWS, that certainly isn't self-hosting. And again the similarity holds: when you operate a computer brand and it's all off the shelf parts you're not really a computer builder, even if the exact same configuration would nicely run under "I built this" when some by a consumer.
Self-hosting is broad enough to include wanting to get away from large centralized vendors and take hosting into your own hands. Owning your domains and being vendor agnostic with IaC.
You won't get any server side CI/hooks or even multi user management, but if you just want a central place to push and pull your private code it's perfect.
I mean, on one level, a plain directory is also a generic interface, but blob storage has semantics which naturally lend themselves to replication in ways that a regular filesystem doesn't.
... why not just use the cloud at that point and skip having to roll your own everything?
Self-hosting, with emphasis on the self, to me is taking it into your own hands.
Using the cloud can be very liberating these days, you can do it in a vendor agnostic way where you own all your domains, your data and can move freely between any cloud provider.
Also more expensive of course.
To me self-hosting was always about freedom. The two arguments against self-hosting in the cloud are security and cost.
in the past have used git-remote-gcrypt[1] with rclone.
currently using git-remote-aws[2].
both work great.