Do you see any use cases or benefits for creating a devcontainer for Geodesic?

I do want to - like the one we have for Atmos

I can take a crack at it! Do you envision having it similar to the Atmos devcontainer with a quickstart?

Yes, though we don't have a home for a quickstart yet. We want to launch a micro site for geodesic as well.

Sweet, sounds good! I can take a crack at it this week

There is an atmos devcontainer?

Yep, there is!

If there is documentation or old office hours where this is covered, please link me to it

Sorry, brand new to GitHub. Will this launch the codespace under cloudposse org?

No, it will be under your github

The note on the linked page implies that it's free to give it a try?

Sweet, I just wanted to see a quick demo without it being on a bill somewhere I have to answer for 😉 Will let you know how it works out. YOLO, right

Note, terraform is painfully slow on machines with lower memory / cores

Yeah, that's my concern. Anecdotally it feels like terraform is slower in geodesic as well on my m3.

You would need to place the cache on the mounted filesystem in geodesic

So, is the Codespaces demo just to demo the devcontainer, or do you actually use it? (ie does it handle authentication into AWS, etc)

It's just a demo. At this time, we predominantly use geodesic

@Jeremy G (Cloud Posse) I’ve created a basic devcontainer for Geodesic in a draft PR (https://github.com/cloudposse/geodesic/pull/957). You’re welcome to build on it or disregard it entirely. The Geodesic container starts up, but the prompt doesn’t display—I suspect there’s some initialization magic happening behind the scenes that isn’t working.

@Michael Here is the (slightly sanitized)

devcontainer.json

I use for your customized Geodesic. See if there's anything you'd like to take from it and add to yours and please LMK what you think.

{
  "name": "Geodesic Dev Container",
  "image": "<your-GH-org>/infra:latest",
  "mounts": [
    "source=${localEnv:HOME}/.aws,target=${localEnv:HOME}/.aws,type=bind",
    "source=${localEnv:HOME}/.config,target=${localEnv:HOME}/.config,type=bind",
    "source=${localEnv:HOME}/.emacs.d,target=${localEnv:HOME}/.emacs.d,type=bind",
    "source=${localEnv:HOME}/.geodesic,target=${localEnv:HOME}/.geodesic,type=bind",
    "source=${localEnv:HOME}/.kube,target=${localEnv:HOME}/.kube,type=bind",
    "source=${localEnv:HOME}/.ssh,target=${localEnv:HOME}/.ssh,type=bind",
    "source=${localEnv:HOME}/.terraform.d,target=${localEnv:HOME}/.terraform.d,type=bind",
    "source=${localEnv:HOME}/.bashrc.d,target=${localEnv:HOME}/.bashrc.d,type=bind"
  ],
  "workspaceMount": "source=${localWorkspaceFolder},target=${localWorkspaceFolder},type=bind",
  "workspaceFolder": "${localWorkspaceFolder}",
  "appPort": ["12345:12345"],
  "containerEnv": {
    "SHELL": "/bin/bash",
    "GEODESIC_PORT": "12345",
    "GEODESIC_HOST_CWD": "${localWorkspaceFolder}",
    "GEODESIC_WORKDIR": "${containerWorkspaceFolder}",
    "LOCAL_HOME": "${localEnv:HOME}",
  },
  "remoteEnv": {
    "LOGIN_SHELL": "/bin/bash"
  },
  "settings": {
    "terminal.integrated.defaultProfile.linux": "/bin/bash"
  },
}

Note that

appPort

and

GEODESIC_PORT

have to match, but otherwise can be any non-privileged port.

@Jeremy G (Cloud Posse) I assume that

localWorkspaceFolder

is set to the directory on your host machine that contains infra?

IIRC,

localWorkspaceFolder

is a devcontainer standard that refers to the folder which the IDE has opened as the root of the project. So yes, it is the root of the Git repo, containing the

components/

and

stacks/

directories.