# Uncloud Server Setup


I'm thinking about "upgrading" my server from Ubuntu to Fedora and thereby also making
[Uncloud](/tags/uncloud/) a part of my routine, _but_...... This can be done, but doing a container style
setup, does mean I need some extra infra, like a container registry, also my DNS server needs to set source IP
addresses for notifies unsure if that will still work.

And Caddy with L4 forwarding _and_ getting TLS certificates can cause issues, because
it interferes with each other (i.e. Caddy is starting, but not L4-forwarding, aks for a certificate, DNS is
still not working, cert is not handed out - that kind of thing).

Still I do like to play with it, so I will need:

- 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...

I'm worried I'm painting myself in a corner and create some kind of cyclic dependency, but I think I should be
fine.

This makes my server less dependent on the actual OS it is running _and_ allows my playing with Uncloud which
I'm starting to like more and more.

Probably wise to start with the minimal stuff and go from there.