[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNTA2MDI","title","Self-Hosting for busy web developers","state","published","contactAuthorMethod","email","aboutText","

Self-Hosting is no whichcraft.

It is just a skill like any other. It gets hard really fast because infrastructure inherently is hard. But as a single developer or indie hacker you are not an enterprise. You do not have an SLA with 99.9999% uptime. You just want to run one or more applications in a cost-effective and easy way to validate your bets.

We will check out the cloud providers next to Big Tech. Choose an operating system and install docker. Set up some basic security measurements, and automatic updates for the OS and your containers. Look at web servers and DNS providers. Choose a monitoring solution, and set up backups.

No Kubernetes, no clusters, no complex stuff. No new tool for automation. A good old one-time hands-on setup and you can call it a day and have a platform for all your ideas and bets to come.

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci81MzQ3Ng","name","Andrej Friesen",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/1272762/medium/Andrej_2000x2000.png?1651132211","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author