kocyigityunus

The book was released 3 months ago and I shared it on HN. Since it didn't get the attention I expected (Show Your Work by Austin Kleon), I decided to repost it with a new title and a new description.

I’ve been working on this for nearly two years, originally aiming to complete it before my child was born, but he’s now 16 months old. Go figure. Seems like writing a book is harder than it looks. My original motivation was to write something I would want to read since most resources on self-hosting (actually most resources on anything) were too shallow, lacked real-world examples like code, or didn’t fully address the knowledge gaps I kept running into.

The book starts with the basics and builds up to covering the full infrastructure stack, with the goal of understanding the system as a whole and deploying on Kubernetes. Kubernetes is a major focus of the book, but the content (and the ideas) can be applied to any environment. It's hard to do this justice here, but you should probably check the sample "Jobs and CronJobs" section to get an idea. There’s also a section on best practices, tips, and practical details based on things I’ve run into myself.

It is available for free including the PDF and the code blocks. Yet, you are welcome to pay what you want.

the most important task.

that's what our ai landlords want. i will give them that, and a few years later i will resell them the cure.

some says don't use the word book, some says use manual but it's old fashion. guide is not probably it for 750 pages. idk.

alternative method probably means a coin.

you can just skip parts.

also, happy to discuss if you just can tell me the client program and the device you are using.

no, it's not. pdf has multiple rendering modes and your problem is the client you are using to view it.

the reason this book being ~20 mb with 750 pages is that %99 percent of the things inside is vectoral, including the variable font that I used. While trying to find the perfect page aspect ratio and the perfect variable font width, I tried it with many different screen sizes, operating systems, dpis etc and clearly tell you that you have another problem.

Probably not that light.

Maybe. Please read it and tell me if it helped fill the gaps, since that was the main point.

You're welcome. Please read and share it.

Most publishers wanted me to split it into two or three parts. However, doing so would require splitting it at awkward points.

Additionally, I’ve spent so much energy writing it that I didn’t want to deal with that.

A standard color book with 800 pages will be around $25 at scale. So, if I sell it for ~$40, I would make ~$5.

Since I spend so much time, I decided to let people read it.

Thank you. It was the hardest thing I've ever did by far.

Let me add that and come back to you.

Thank you.

I talked with several publishers. It seems a 750-page, high-quality printed book just isn’t economically viable these days.

what is the operating screen, the app you reading on and the model of the phone ?

I’ve been working on this for nearly two years. I originally aimed to complete it before my son was born, but he’s now 16 months old. Go figure. Seems like writing a book is harder than it looks. My original motivation was to write something I would want to read since most resources I found on self-hosting were either too shallow, lacked real-world examples like code, or didn’t fully address the knowledge gaps I kept running into.

The book starts with the basics and builds up to covering the full infrastructure stack, with the goal of understanding the system as a whole and eventually deploying on Kubernetes. Kubernetes is a major focus but the content can be applied to any environment. I can't express this clearly, but you should probably check the sample "Jobs and CronJobs" section to get an idea. There’s also a section on best practices, tips, and practical details based on things I’ve run into myself.

It is available for free including the PDF and the code blocks. Yet, you are welcome to pay what you want.

You claim that your library can build landing pages. Yet, your hero image on the landing page is a dashboard.

great design. loved it.