I have migrated this site from Codeberg Pages</a> (and
before that, sourcehut pages</a>1</a></sup>) to a VPS. This is something
I've been considering for a long time and finally got around to it this week,
in no small part encouraged by recent discourse (see: one</a>, two</a>, three</a>).</p>
I already moved off GitHub many years ago, seeing the, uh, direction, it was taking
after the Microsoft acquisition... I remember when GitHub used to be a good
example of a lightweight website, but much ink has been spilled already on its
overall degradation (see above, also four</a>).</p>
I've also set up my server to host my git repos</a>, inspired by the post Git
without a forge</a>. This amounts to a bunch of bare repos and cgit</a> as a
frontend.</p>
However, for now I will continue using Codeberg</a>
for public projects for exposure, reachability, ease for potential contributors,
etc.</p>
This site and everything in this domain is running in a cheap VPS (1 vCPU, 1GB
RAM) with nginx. Using Tailscale</a>, I can very easily access it remotely. I use
Zola</a> for the static site, building it on my computer and scp'ing the
generated HTML over to the remote server2</a></sup>.</p>
For the git 'server', I created a Contingency measures to deal with higher traffic load (nginx cache? rate
limiting? anti-crawler blockers (Anubis</a>?
Iocaine</a>?).</p>
</li>
Performance/load monitoring tools (Grafana?).</p>
</li>
A personal fediverse server, considering some lightweight options:</p>
Run the actual server locally (I have an old Raspberry Pi around, or an old
laptop..) and keep the VPS just as a reverse proxy that essentially tunnels
the local server over tailscale, maybe with caching and anti-bot filters on
top of that. That way I get to run the server locally without exposing my
home IP. I like the idea of my servers being something I can physically
access.</p>
</li>
</ol>
And before that</em>, GitHub Pages. I gotta keep this one around for
something I made that the OoT speedrunners
use</a>, or at least just that page. ↩</a></p>
</li>
I could</em> automate this step by having a post-receive hook in the server
that runs Git</h1>
Setup</h1>
git</code> user with its home in /srv/git/</code>,
where the bare repos live. This gives me write access to it via ssh with a
remote like git@<VPS tailnet IP>:<repo name></code>. I have the actual VPS
firewalled to reject all traffic except for HTTP (port 80) and HTTPS (port
443), so I can only SSH to it via tailscale, which is good for security
(probably). I also support regular HTTPS cloning. For the frontend I use cgit</a>
as mentioned. It integrates easily with nginx, is lightweight, and has a
configurable cache. I've lightly customised its CSS.</p>
TODOs, Future Plans</h1>
zola build</code> when push</code>ed to, but it's fine like this. ↩</a></p>
</li>
</ol>
</section>
This page cannot be shown here. You can still read it on the original site — the toolbar below keeps your place in the directory.
I have migrated this site from Codeberg Pages (and before that, sourcehut pages 1 ) to a VPS. This is something I've been considering for a long time and finally got around to it this week, in no small part encouraged by recent discourse (see: one , two , three ). Git I already moved off GitHub many years ago, seeing the, uh, direction, it was taking after the Microsoft acquisition... I…
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.