[HN Gopher] Soft-serve: A tasty, self-hostable Git server for th...
___________________________________________________________________
Soft-serve: A tasty, self-hostable Git server for the command line
Author : thunderbong
Score : 81 points
Date : 2023-03-27 16:41 UTC (6 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| MatthewPhillips wrote:
| I'm very curious what their business strategy is.
| nerdponx wrote:
| Their website implies that they are available for hire for
| enterprise consulting.
| johnea wrote:
| This is all uinclear to me.
|
| --> pacman -S ssh git
|
| Voila, you're self hosting a git server...
| nerdponx wrote:
| Right, but you could easily end up writing a bunch of custom
| automation scripts and/or APIs around this, at which point
| (unless you really like DIYing stuff) you might better off with
| something like Soft-serve.
| qbasic_forever wrote:
| Now manage users and granular user-level access to repos...
| it's doable but you're going to write a boatload of one-off
| scripts and hacks, which tools like soft-serve have already
| implemented.
| garganzol wrote:
| The project has interesting approach to UI: differences between
| GUI and CUI (aka console user interface) are almost erased.
| 8organicbits wrote:
| All of the https://charm.sh/ tools are beautiful like this.
| I've been looking for an opportunity to build on these, but
| haven't had a chance yet.
| nacs wrote:
| Those TUIs makes me want to learn Go..
|
| (Does anyone know alternatives to this for nodejs though?)
| INTPenis wrote:
| 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.
| sdfhbdf wrote:
| S3 sounds very inefficient for storing git objects. Unless
| you're talking converting git protocol to S3 Object Versions
| API which might sound like an interesting project.
| INTPenis wrote:
| I only say S3 because it's a cheap type of online storage
| that does not require any of your own infrastructure.
| ikiris wrote:
| so you want to self host via the cloud?
|
| ... why not just use the cloud at that point and skip
| having to roll your own everything?
| INTPenis wrote:
| That's not SELF-hosting.
|
| 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.
| nicoburns wrote:
| There's a sense in which using the cloud isn't SELF
| hosting either. Although I get what you mean.
| interroboink wrote:
| > 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_...
| scooke wrote:
| Self-host is the right term. They install and host their OS
| or software themselves on a VPS, NOT a homeserver or VM.
| Until they set it up, there is no "cloud". "Cloud" IS a
| service, OS, etc that someone else set up and which you (pay
| to) use, and which that someone else ultimately has control
| over.
|
| 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).
| INTPenis wrote:
| Yeah that used to be it for me too, until I got rid of all my
| possessions and started living more minimalistic.
|
| 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.
| qbasic_forever wrote:
| Check out rsync.net, it allows you to use git and ssh on its
| storage infrastructure. Create bare repos there and you can
| push/pull just like from github:
| https://blog.kozubik.com/john_kozubik/2010/02/git-and-subver...
|
| 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.
| [deleted]
| benatkin wrote:
| Hmm I'm sold on git over https. One of many things that forgejo
| has right.
| eddieroger wrote:
| I love days like today, $SYSTEM goes down, then we get a thread
| about $ALTERNATIVES, and now posts about $ALTERNATIVE[X].
|
| I like the look of this and the other stuff from the folks behind
| it, but I'm curious if anyone is using it "for real." I would
| love to use this over others with web UIs, but at this point I am
| also in the market for Git+Actions-analog, which Gitea and Drone
| (and now just Gitea) fill on their own. Am I missing the mark on
| this tool's use case, or is it not just to the place where it can
| do such things yet.
| capableweb wrote:
| Soft-serve is not really an alternative to GitHub, unless you
| literally only use GitHub for the git functionality itself, but
| then you could just use any Linux server + openssh + git to get
| basically the same functionality. But I see people tend to use
| GitHub for much more than just Git, for better or worse.
| jonas-w wrote:
| I wish that this TUI could integrate directly with gitea or
| gitlab and wouldn't be a standalone server.
| candiddevmike wrote:
| Slightly OT: how feasible is it to do issue management as
| markdown within a monorepo, anyone have any experience with this?
| Fossil does this already, but I think git could do it just as
| well?
| raggi wrote:
| Still using gitosis, and still happy with it.
___________________________________________________________________
(page generated 2023-03-27 23:00 UTC)