How to set-up acorn.io & minikube correctly

The commnand "minikube start --container-runtime=containerd" should yield

The command "minikube addons enable ingress" should yield

The command "acorn install" should yield

The command "minikube tunnel" should yield

        Now when running "minikube tunnel, it will only ask for a password when a service that needs to use the ingress-nginx service to port expose an application on port 80 or 443 or 53, etc. The point is that build, run, update, and push are the final steps. Due to how it simplifies things for building, running, testing, and then deploying, it makes it easy to test what will and won't work. But it also simplifies production of applications. If your developers or an up and coming software developer, one thing you'll find hard is getting something out into production code. For me, it was more finding how to simplify the deployment of web apps I was trying to initially build so they would run in a production environment with the least amount of conflict.

        Many times, things are over-engineered about the web. And while it has a reason for such, it could also be re-engineered, as optimization took that aspect of the web down the wrong development pathways. The one step I didn't see asked often is "is what we're working on over engineered?", "is what we're doing 'just the minimum' as described? Where did someone solve for a y-problem? Am I attempting to solve one now?" before they dive into the industry.

        When I develop code for the web, I have it only be the logic needed. Anything more than 3 javascript libraries or it has to be nodejs javascript specificly, I steer clear from to avoid the problem wordpress has. Same principle applied to things with too many dependencies to any app I build. When I build an app, it should have as few running and moving parts as possible. Kubernetes is a large and diverse tool. So, finding a simpler solution that built off of it while keeping the number of resources, namespaces, pods, and deployments low as possible in count was a must.

        When I learned what acorn.io could do on kubernetes after DevOps Days in 2023 (May -- Austin texas branch of DevOps), I took a look into how their tool works. Well, today, August-20th-_-2023, I figured out that the above method was simple and close enough without all the complex configuration metadata in yaml files. This approach has actually saved me several headaches for creating websites, but also defining more complex applications with the least number of high-level of abstractions required.

        Now many others can also have a shortcut.