Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
The Forgejo guys have built this themselves, so I'm aiming to use that (I don't just yet, because I can't find the time).
I’ve tried it with forgejo, the recommended implementation involves spinning a temporary vm to run the integration and deployment processes, quite resource heavy and slow comparatively to the vm I have that’s running forgejo.
I think there’s an option to have the forgejo server itself run the commands without spinning up vms, but it’s not recommended due to security considerations as they’re running with the same privileges as the server - not a concern if you are the only developer connecting to a private instance of forgejo but something to keep in mind.
Its quite complicated to setup as well, just went through the instructions and its a long way from just add to docker and run unfortunately. Would be nice to be able to just get a runner in the same or different docker and it just works easily without a lot of manual setup in Linux of directories and users and pipes etc.
Just to contrast with some of the other comments regarding this, i've have a pretty good experience with this. Was fairly simple to setup up some docker-based runnings following their admin guidance. Have set up a couple (One for Codeberg, one for my own Forgejo instance) each via a seperate LXC container on my home lab. Has been relatively simple to administer so far.
The actions format may take some getting used to if not familiar with GitHub's own actions CI, which if closely emulates, but most of my projects were coming from GitHub anyway.