Hacker News new | past | comments | ask | show | jobs | submit | omerh's comments login

I did almost exactly the same yesterday.

https://blog.omerh.me/post/2019/05/17/first_post/


Nice theme, I built one some months ago I found none to my taste, so I modified my own

https://xaviondono.com/

Now I just need to start writing


Plus you've invested a little in finding a nice theme :)


My default search engine for more than a year. Mobile and desktop, rarely I use !g bang.

Also, dns are 1.1.1.1 / 1.1.0.0 Browsers are ff and safari. Email is ProtonMail.


Did a complete refactor to do it more efficiently


Did some refactoring :) thanks for noticing ... It's now far more efficient from a small test I've did


A Tiny container to watch other containers on a docker host, once the other containers exits, gowatcher will terminate and reduce autoscaling group count


With www Optional wize: easy dns handling and wildcard ssl will serve any other future sub domain dns. Seo wise: google prefers it And if I’m not mistaken there and rfc for it. I can look later


Sorry for the typos. Operational wise

There is an RFC for using www


I’m using ProtonMail with the free plan for more than 6 month now, still have some husk from Gmail being auto fowrorded to it. And for work I use gsuite for now.

ProtonMail only did one thing wrong lately. They’ve added a payers feature a @pm.me short domain and allowing for the free users to only receive emails with this address. That was irritating and absurd, so I’m still thing if I want to move to move completely.

Fastmail recycling makes them irrelevant.


I moved to the free version of protonmail. Having my gmail fw all emails to this account.

It was this or managing my own mail server. For now I’m happy with thier service and their privacy policy of course. But, it’s not gmail or even close to it feature wise.


Easy way to terminate instance from within it. Making sure you are terminating the right one without autosclae policies


For multiple layers in a Dockerfile use overlayfs2 and not aufs. You will suffer from slow io


I've been having issues with slow IO on some of my containers, and I'm using AUFS. What is the cause of the slowdown with AUFS? Why do they not use Overlay2 as default if AUFS has such a major issue?


AUFS is the only fs that was broadly distributed until recently. Now, it's been removed in the latest linux distributions because it's too buggy and unstable.

Overlay was started and quickly abandoned. Only to be replaced by overlay2 that is work in progress and not wildly available yet.

This article contains a bit of history on Docker filesystems: https://thehftguy.com/2016/11/01/docker-in-production-an-his...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: