Ask the main part of your question in the title. This should be concise but informative.
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
first: why do you even need k8s just for your portfolio website? what features does it provide which is useful to you?
you have to install minikube on your old laptop to be able to run pods etc
tbh you dont need k8s, plain docker container would do and if you want to be fancy use docker swarm :)
I know it’s overkill :) Wanted my README to have 1 installation command instead of 2 for easy review. Also showcase skills that go beyond Junior level.
Initially I decided against kubernetes but since podman already has it integrated, why not? This way, I eliminate the need for podman-compose install. My app is part of the portfolio, has 3 containers for frontend, api and database. Didn’t finish the personal website yet, lol.
Didn’t know about docker swarm and I definitely want fancy :)
You need to be able to pull or build the images on the other machine. At a company you would use a private container image registry on something like GitHub, GitLab or JFrog.
Setting up a GitLab instance is a really cool homelab project that can also go on your portfolio.
Develop on your workstation, push to the registry on machine B, pull from that and run on machine B
That clarifies things, thanks! I’m definitely interested setting up a proper homelab
Glad to help. Have fun!