Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)EL
Posts
0
Comments
141
Joined
2 yr. ago

  • Container orchestration is what you're looking for. Kubernetes is the most popular, but it might be overkill it's hard to say based on your setup. However it's definitely useful experience to know how to run it.

  • When you login to a website they need to give you a secret password so that when you go to the next page you can tell them that secret again and they will let you access information you have permission for (your Facebook wall for example). That secret is stored in a cookie and every time you go to another page the cookie is sent to Facebook so they know who you are again.

    In this instance a cookie is the wrist band you get at a concert so they can easily check that you purchased a ticket. You don't want to have to show your ticket every time you leave and come back into the concert because that's slow, you just flash the wrist band and they let you in.

  • We use Rancher fleet. It monitors a repo for k8s YAML files and applies them to the cluster automatically. But that doesn't sound like it would work for you.

    As for PRs, I'm sure you can setup a GitHub workflow to automatically merge PRs (I'd make sure to filter them by the author though).

    For the images without proper versions you can always use the Image ID as a pinned reference to a specific image. Though whether that same image is still in docker hub is a different story.

    A lot of your wishlist could be done quite easily with kubernetes. The automatic update isn't built in but tools exist to help you with that (even rancher fleet).

  • I've found most places aren't very good at explaining the system design. Just make one yourself from what you understand, that'll help you figure out how the system works, and your team will usually correct anything you got wrong (assuming it's small enough to quickly review and notice incorrect assumptions).

  • I feel like agile is better for Apps (which requires very little documentation usually, no one wants to read a help guide for an app), compared to Libraries which are literally unusable without documentation.

  • I can run GitHub workflows directly on my machine with ACT, I'm sure you could run that on your own private CI if you needed too. It's not perfect, but if a lot of people started wanting to migrate I'm sure it could get better.

  • I typically run postgres locally too (in docker), while there's still technically network overhead there's not much compared to a real network, plus you can easily move it to another machine without reworking your app to switch from SQLite to postgres.