161–170 of 285 posts
We kind of moved away from this monolithic setup tho. Oh you can scale-up your hardware like we used to, it will work, until some point. And the day you will need to split your services will come quickly. This is a perfect solution for early stage projects if you're in a startup or for a personel project, but monoliths are....well....monoliths.
monoliths are KISS, and kubernetes can be YAGNI
Earlier quoted context omitted.
I like this. Out of curiosity, could you share your bash script?
I do not want to clean it up from some revealing things, so no. But it is fairly trivial. If you are an experienced programmer you would not have troubles writing one up one yourself in no time.
Traefik Proxy[0] was a game changer for my self-hosted setup of Docker containers. Traefik can read labels applied to Docker containers (easily done with docker-compose) and setup the proxy for you as containers come and go. Even maintains the Lets Encrypt certificates seamlessly. [0] https://traefik.io/traefik/
I’m using the same server type from OVH in Hillsboro and it’s great. They frequently do sales. Highly recommend anyone interested to go for the nvme upgrade. I rent three now total, one for production sites, one as a development machine strictly for vscode and another for development / staging / misc. waaaaaay overkill but it’s been a huge quality of life improvement. For containers I just use a couple docker compose…
Earlier quoted context omitted.
> > "an API for everything" > Not sure what you mean here. I assume referring to APIs for controlling and monitoring the infrastructure, not anything about APIs you may provide in your application or consume from external sources.
What infrastructure? Thanks to my primitive approach I hardly have any.
I'm doing something similar though I've opted specifically to _do_ use Kubernetes via k0s [0]. It works wonderfully well and allows me to use most things that are available in the k8s ecosystem like cert-manager [1] and external-dns [2]. All configuration is stored in Git and the server itself is basically disposable as it only runs k0s and some very basic stuff like iptables rules. I see this sentiment quite a lot t…
Do you have any estimates how resource hungry k0s is? Ran few resource constrained k3s clusters, where 25% of cpu was always spent on running k3s itself.
So yes, it definitely takes quite a bit of resources. I'm running this on 4 CPU cores and 6 GB memory, so 25% of 1 core and some 600mb of memory still leaves plenty of resources for the services. On a more philosophical note (as was mentioned below in this thread), it is a bit wasteful perhaps.
I do something similar: - GCP VM with “Google Container OS”. - “Cloud init” config set on the VM metadata (can easily recreate the VM; no snowflake config via SSH mutations). - My service runs in a docker container, reads/writes to a SQLite file on the host disk. - GCP incrementally snapshots the disk every hour or so, and makes copies to different region. Any disk writes are copied instantly to another zone. - Lets…
Earlier quoted context omitted.
What infrastructure? Thanks to my primitive approach I hardly have any.
If you want to dynamically provision storage or grab an extra instance when you’re under load or something. It’s handy to not have to sit on a bunch of storage you’re not using just in case there’s a rush.
Old-school dedicated servers are so cheap that you can match a startups' peak autoscaled load and still pay less than their "idle" load.
Later...
> I host my own analytics ... They provide an open-source, self-hostable version which I have it deployed with docker-compose.
Wouldn't docker-compose be the "already doing it" answer to the first question? It's pretty much your library of 'exact docker run commands', plus sugar to manage the running ones collectively.