What is the best way to use hatch in devcontainer.json on GitHub Codespaces?

[antonymilne]

I'm using Hatch on a project and would like to use GitHub Codespaces. There is a Hatch feature available, but it doesn't appear to be well used.

So I'm wondering what would be the best pattern to follow here. Ultimately, what I'd like is a fast and efficient system that opens up Codespaces that has at least Hatch's default environment, and ideally others, already created (i.e. hatch env create ...). This way the user shouldn't need to wait for the environment to be installed on the fly when they open a new Codespace. I believe there should be some good way to achieve this using some appropriate lifecycle scripts and possibly tinkering with Hatch's cache setting.

Has anyone done this before? 🙂 I can probably figure it out myself if not, but I thought others might be interested in this topic too so best to start a discussion anyway.

[Anchorfall]

Having a similar issue. Did you ever find a solution?

[antonymilne]

Not really - I got something that worked ok but didn't spend any time optimising it to use caching or similar. https://github.com/mckinsey/vizro/blob/main/.devcontainer/devcontainer.json. If you can think of any improvements then I'd love to hear.

[Anchorfall]

Yeah, I also ended up going the 'postCreateCommand' route in the end. Also configured hatch to create the environments in a .gitignored folder on the mounted workspace directory, so the environment files will persist on the user's drive (not sure if that applies to your situation, I'm not using GitHub Codespaces and don't know much about it). Works well enough, and we don't have time to come up with anything better