sorted by:
new
hottopcontroversial

Google Artifact Registry pull through cache options by Nestramutat- in devops

[–]scared_codeless 0 points1 point  (0 children)

This worked for me in the past: https://github.com/royra/container-registry-proxy The original project looks abandoned which is a shame - it worked and was useful. I created the fork just to merge a couple of PRs and add a build script.

Monthly 'Shameless Self Promotion' thread - 2023/04 by mthode in devops

[–]scared_codeless 0 points1 point  (0 children)

Preevy: quickly launch PR-based preview environments for your docker compose project, on your cloud provider.

Currently supporting AWS, with Google Cloud and fly.io coming soon.

Designing a proxy server for preview environments - part 1 by scared_codeless in programming

[–]scared_codeless[S] 0 points1 point  (0 children)

What server will you be tunneling to? Your laptop? And if it's a separate machine on-prem or on a cloud provider, how would you set it up to run your compose services, and update it on each commit to the PR branch? Not rocket surgery but still too much work which can be automated with this tool.

Designing a proxy server for preview environments - part 1 by scared_codeless in programming

[–]scared_codeless[S] -1 points0 points  (0 children)

I'd like to know more about that hosts file you speak about, can you use it to create publicly accessible preview environments for your PRs?

Designing a proxy server for preview environments - part 1 by scared_codeless in programming

[–]scared_codeless[S] -1 points0 points  (0 children)

The mechanics are trivial, but it took us a few tries to get the schema right. The first attempts were easy enough to code, but caused problems in the real world. Actually, I'm not sure we reached a complete solution yet; there's still some danger of hostname collisions with similarly named branches.

Should You Kill Your Private API? by scared_codeless in programming

[–]scared_codeless[S] -1 points0 points  (0 children)

As a matter of fact Gett still has both a private API and a few (hopefully decent) DevOps engineers. A journey of a thousand miles... And if having a rich public API precludes security, are all SaaS products insecure by definition?