I’ve been looking for th8s for awhile too.

Not a locally run tool, but a self hosted web app (that I wire up to my self hosted db) that has a web portal I login to, and then can manage my db with a nice slick UI to define tables, relations, etc.

There’s been some I’ve found but they vastly lacked basic features and were clearly in very early beta.

I use Hugo, it’s not super complicated.

You basically just define templates in pseudo html for common content (header, nav panel, footer, etc), and then you write your articles in markdown and Hugo combines the two and outputs actual html files.

You also have a content folder for js, css, and images which get output as is.

That’s about all there is to it, it’s a pretty minimalist static site generator.

Hosting wise you can just put it on github pages for free.

Dunno why ppl are down voting you, this is 100% the way.

Architecture as code is amazing, being able to completely wipe your server, re-install fresh, and turn it on and it goes right back to how it was is awesome.

GitOps version controlled architecture is easy to maintain, easy to rollback, and easy to modify.

I use k8s for my entire homelab, it has some initial learning curve but once you “get it” and have working configs on github, it becomes so trivial to add more stuff to it, scale it up, etc.

They genuinely looked identical to me.

Either way, gogs dies what I need it to, git server for backing up my code and super basic git web Hooks to trigger my build server.

Couldn’t ask for anything more.

Gogs and Gitea are very similiar, Gitea is a fork of Gogs with a bit more features as I understand it.

However when I tried to get Gitea working personally a year and a half ago, it had some rough issues with redirect looping onto itself infinitely, could never get it to work.

On the other hand Gogs didn’t have this issue, and was much more painless to stand up, so it’s what I use now.

No problem, the mode you are looking for is called Bridge Mode, and what you’ll need to ensure your setup is, is:

ISP -> ISP Router -> Your Router -> Rest of the network

It’s crucial you only have your router as the only thing plugged into the ISP Router, and you want it to be typically plugged into port 1. You’ll need to either look up the paperwork or talk to your ISP about how bridge mode works for their modem model.

Keep in mind once bridge mode is enabled on the ISP router, it loses its wifi network so the only way after you can connect to it to configure it is by a physical connection, so if you mess it up you’ll need to have a laptop or smartphone you can physically connect via ethernet to port 1 of the isp router to be able to access its interface again.

But once you get bridge mode working your private router will now get a public IP assigned to it instead and it will act as the “real” router of your network.

You will need to open some ports, but ideally you just open up 1 port for a VPN and call it a day.

If you want a really easy solution you can buy one of the mid to high end routers that comes with a built in OpenVPN you can enable, and you just do the process to have it be the router for your network (usually by setting your modem to pass through mode and then have your personal router immediately next in line, and it becomes the actual router of the network)

If you do a search you should find a few decent models out there with OpenVPN support, and then its just a matter of enabling the feature in the router’s interface and following its guide and then installing OpenVPN on your mobile phone(s)