I don't want to have to authenticate a local dev container if the host machine is already configured

[petebachant]

Adding something like:

  "initializeCommand": "bash -c 'echo \"CALKIT_TOKEN=$(calkit config get token)\" > .env.temp' && bash -c 'echo \"CALKIT_DVC_TOKEN=$(calkit config get dvc_token)\" >> .env.temp'",
  "mounts": [
    "source=${localEnv:HOME}/.calkit,target=/home/vscode/.calkit,type=bind,consistency=cached"
  ],
  "postCreateCommand": "bash -c 'source .env.temp && echo \"export CALKIT_TOKEN=\\\"$CALKIT_TOKEN\\\"\" >> ~/.bashrc && echo \"export CALKIT_DVC_TOKEN=\\\"$CALKIT_DVC_TOKEN\\\"\" >> ~/.bashrc && rm -f .env.temp'",
  "updateContentCommand": "while ! docker info > /dev/null 2>&1; do sleep 1; done && conda init bash && . /opt/conda/bin/activate && calkit check envs",
  "postStartCommand": ". /opt/conda/bin/activate; mkdir -p $HOME/.cache; calkit config github-codespace > $HOME/.cache/calkit-config.log 2>&1 || true; calkit pull > $HOME/.cache/calkit-pull.log 2>&1 || true"
}

to the dev container spec works, but we probably want to ensure this is robust when running in Codespaces.

[petebachant]

To make things more sustainable and allow "automatic updates" we may want to move this into a script in the container image, so the latest image will always have the correct init commands being run.

[petebachant]

We could also consider removing the mounts and running calkit config... in the init steps.

  "initializeCommand": "bash -c 'echo \"CALKIT_TOKEN=$(calkit config get token)\" > .env.temp' && bash -c 'echo \"CALKIT_DVC_TOKEN=$(calkit config get dvc_token)\" >> .env.temp'",
  "postCreateCommand": "bash -c 'source .env.temp && calkit config set token $CALKIT_TOKEN && calkit config set dvc_token $CALKIT_DVC_TOKEN && rm -f .env.temp'",
  "updateContentCommand": "while ! docker info > /dev/null 2>&1; do sleep 1; done && conda init bash && . /opt/conda/bin/activate && calkit check envs",
  "postStartCommand": ". /opt/conda/bin/activate; mkdir -p $HOME/.cache; calkit config github-codespace > $HOME/.cache/calkit-config.log 2>&1 || true; calkit pull > $HOME/.cache/calkit-pull.log 2>&1 || true"
}

[petebachant]

We may want something like a calkit config to-dotenv -o .calkit/temp/.env command to dump important config values