creztoe

7 ms·

1.
by creztoe 6y ago
That sounds awesome and also a huge headache. I've found its much easier to work with an ORM that is specifically designed for GraphQL, like TypeORM[1]. Otherwise you are just kind of trying to force a square peg in round hole (like Gr
2.
by creztoe 6y ago
That's how I understand it. Basically you have a machine hosted somewhere with a dedicated IP so you can access all remote machines from anywhere at any time, as long as they are connected to it via reverse proxy.
3.
by creztoe 6y ago
Do not pass sensitive data to docker build via --build-arg. When you access this with "ARG" you will log the information in the docker history, visible to all. Use "--secret" or use the ARG in an intermediate build stage
4.
by creztoe 6y ago
This kind of confuses me a bit. Why would you want to turn Pub/Sub into a queue? How badly does this affect message acknowledgment and retries? I assume just a huge hit to latency. This seems like a horrible idea for anyone expecting t
5.
by creztoe 6y ago
Maybe it's just me, but I didn't get that from rozab's comment at all. I figured the point was something like, "Why is this project unique? Maybe the time would have been better spent contributing to an established proje
6.
by creztoe 6y ago
This seems like it's just a click-baity ad for their productivity analysis tools. I struggle to find a single thing of value in this post.
7.
by creztoe 6y ago
I'm lazy. I've found a gitlab wiki sufficient for my basic needs. 1. Version control 2. Easily editable from terminal (markdown) 3. Easily viewed via browser (either on gitlab or self hosted gollum instance) 4. Supports some HTML,
8.
by creztoe 6y ago
Could you explain why helm is garbage? I think it suits its purpose rather well without being too complex. You can essentially "plug-in" different types of resources rather easily. Especially in v3 now that you don't need to
9.
by creztoe 6y ago
Yeah, I was referring to the certbot warning of "logging" the IP publicly. But I guess that policy never actually came to fruition. Thanks for the clarification!
10.
by creztoe 6y ago
I think you are half correct. The gateway has nothing to do with verifying the file during a DNS challenge. However, the IP of the machine requesting the cert IS saved with that cert information and made public. Let's encrypt will even
11.
by creztoe 6y ago
I agree with the confusion. There is the ability to rollout updates in a "wave"[1], but I'm not sure how this is better than a simple rollout strategy in kubernetes since a reboot of the node seems inevitable. [1] https:&#x2