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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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
You need to start with docker.
Get your ci building a docker image of your site
Then host the docker image on a repo somewhere.
Once you have it running in a container you can easily find a “how to” for k8s.
The basics of k8s are:
A collection (or single in this case) of images form a pod (virtual machine) that pod exposes ports to a service.
The service is a single app comprised of a collection of pods (usually only one actually)
The service then needs to expose ports to an ingress (think of an ingress like a load balancer) and the ingress will take the external ports to the cluster and use some magic to forward traffic to you pod
The docker image needs to actually host the site, so more than just files, you’ll need nginx in the image.
K8s is WAY over complicated for this, it’s designed for auto scaling and self healing, but I’m assuming you’re using this as a “cool” or “learning” exercise.
Helm packages for k8s are super helpful and will give you a template for all the networking pieces
That's a nice suggestion. I guess I can make the CI build a Docker image containing my website's files and then have a plugin for it to restart the pod that serves the website so it fetches the latest image.
K8s is that “restart” mechanism.
Docker images are just the thing that it restarts.
Docker itself or “docker compose” can restart images and do everything you need, but if you want to go the full k8s it’s complicated but great learning
One simple way to pull the new image into your cluster is to overwrite the
latesttag, specifyimagePullPolicy: Alwaysin your deployment and then usekubectl rollout restart deployment my-static-sitefrom within your pipeline. Kubernetes will then terminate all pods and replace them with new ones that pull the latest image.You can also work with versioned tags and
kubectl set image deployment/my-static-site site=my/image:version. This might be a bit nicer and allowsimagePullPolicy: IfNotPresent, but you have to pass your version number into your pipeline somehow, e.g. with git tags.