![]() ![]() It also didn't look great on high-DPI screens, and it wasn't dark-modeįriendly either, since each diagram screenshot had a white background. Redo the screenshot, and it made the content repository a little heavier every png in my content repository.īut this had several issues! Any time I wanted to update a diagram, I had to Originally, because I wanted to go fast, I was just taking "area screenshots" ofīits of those diagrams, and saving those as. IĬan live with the occasional one-second "downtime", given that it's all behindįor diagrams, I use (née "draw.io"). ![]() It's not even using any fancy systemd socket activation stuff. Much: I pull futile on the server, rebuild it, save the older binary just inĬase, restart a systemd service, and if it breaks I restore the saved binary and Each deploy points to a set of content-addressed resources, soĭeploying a new version of futile is a bit more complicated, but not that Starts processing those assets, and when it's done, atomically switches over toĪ new "deploy". The production instance of futile detects file changes, and in the background, Shell session $ ssh ftl "bash -c 'cd ~/ git pull'" To "just trust me, the colors are great" and then surrender and just include a Well, so that I can stop apologizing for the lack of colors and tell the reader ![]() Making everything reproducible / automated, it might as well capture colors as In my markdown sources, and have my content pipeline execute them, and since I'm But that's only because I want to write some commands Intro, like: "what kind of asshole needs to looks at large JSON files from a
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |