# Uncloud Server Setup; DONE!


This was the [plan](/2026/july/07/uncloud-server-setup/) and I finally got around doing it. The original list
was:

> - A docker registry for pushing and pulling images too. Maybe I can setup Forgejo to also be a registry, but
>   just the docker registry might be enough. The image comes from Docker Hub.
> - Caddy with L4 forwarding, I can easily make the image myself, and push it to the local registry.
> - S3 storage so that I can make backups with Kopia - probably going to use Garage for this, doesn't need a
>   certificate and should only advertise itself on the internal network - not sure how to do this, without
>   actively blocking.
> - _atomdns_ as a DNS server.
> - _prometheus_ and _grafana_ of course.
> - Git hosting, the server is now holding some **bare** git repos... Forgejo does sound nice...

Note, if you are reading this then _miek.nl_ is served via a docker image through
[Uncloud](https://uncloud.run).

But taking stock of the list, some things did change a little:

- Deployed [Forgejo](https://forgejo.org/), so I have Git repos and a Docker registry.
- Caddy with L4 forwarding for _ssh_, not _dns_, this is be able to use Forgejo.
- S3 storage for [Kopia](https://kopia.io) is not needed, you can do it now with `sftp`, directly on the
  filesystem.
- _atomdns_ is the DNS server, but running as a systemd unit, so outside of the cluster.
- Prometheus and Grafana still to do; wondering what I actually want out of it.