pierrebeucher

You're right cost is an issue, that's why Cloudy Pad is mostly suitable for occasional players (up to 30h or 40h / months) in which case it's still cost efficient to use such Cloud providers.

> more or less identical and cost far far less.

I wish it would, for I have tried: the problem is GPU availability which is often low or highly elastic. Considering data are persisted in a given region, there's high chance your RTX 4090 will be unavailable when you want it.

These platforms are great for AI and inference since you can easily hop onto another GPU type and it's not too much an issue if a certain GPU type is not available at a given time. Not so much for gaming purpose :(

Major Cloud providers have much more availability on their infra.

> Check this out; https://github.com/selkies-project/selkies

Thanks, this is one of the project I had in mind beside Wolf and Sunshine but haven't gone as far. A good reminder to try it out again :)

Do you also use a VPN like Tailscale for out-of-home / remote access ?

Thanks ! Do not hesitate to let me know how it goes if you give it a try

Hi there, I'm Pierre the creator. Work is in progress on this, I hope it will be available in a few weeks since it's a highly requested feature :)

From what I gather it's exactly this in reverse: they already were a consulting company providing development environment to teams as part of their package, and Flox is an internal tool they open-sourced. (interpreted from what I read on their about page: https://flox.dev/about/)

I agree. Plain Nix is very complex but highly configurable and allow very complex use case, whereas Flox / devenv are much easier to setup but hide certain Nix features (which are probably not needed in most dev environments anyway, so it's totally worth it given the simpler interface)

Wouldn't have said better, devenv and Flox are indeed similar and both uses Nix packages. We can say they are different frontends to the same set of packages, with slightly different features.

Both are great in my opinion.

Not too hard, it's one of the source I plan to implement along with Infisical and others. Feel free to create an issue for this :)

Same problem, encountering similar problems with Qwant (though not always)

It seems DuckDuckGo has some kind of outage.

The site itself is not down but every search I did recently are greeted with _Sorry, we ran into an error displaying these results. Click here to try again._

It seems others have the same issue as well considering downdetector data.

Any other people have similar issues?

Working on Novops (https://github.com/PierreBeucher/novops), a FOSS config & secret manager for development and CI. It helps manages secrets securely from various sources (Hashicorp Vault, AWS/GCP/Azure, etc.) across multiple environments. Great for DevExp :)

Novops - https://github.com/PierreBeucher/novops - is a similar tools with active maintenance, more flexibility (generic interface, support plain strings and different secrets providers). Teller is nice but lacks some features Novops aims to provide.

Hello HN ! As developer and DevOps I often lived the painful situation of setting up development environments and CI config when onboarding new projects... A long and difficult path for lots of us.

I started a blog post series to help you leverage tools like Nix, Docker or Novops to setup fully automated, reproducible and secure development environments, I hope you'll enjoy it :)

Can you be more specific about "big players denouncing the 'type of game' development behind BG3" ? I've heard a few things about BG3 development method being critized by some devs and/or companies but haven't read some source material yet.

EDIT: nevermind, Googling "baldur's gate 3 development critics" yields tons of results

Working with Docker for 8+ years I've seen many teams struggling with build process optimization - mostly around CI config for efficient cache re-use. I was surprised very little literature mention that a Docker daemon can be configured as a remotely available server, allowing for a de-facto secure remote cache and build engine.

I've been using this pattern for some time in various teams and projects with great results. Coupled with a simple Dockerfile optimization (and BuildKit cache mount when needed), Docker builds are mostly smooth and painless. It also has the advantage of avoiding overcomplex CI config to optimize cache re-use and vendor-specific cache features.

Your feedback and comments are very welcome as I'm relatively new to this "share your knowledge publicly" thing :)