Skip to content

Developer environment setup: compatible as a Codespaces dotfiles repo.

Notifications You must be signed in to change notification settings

marzvrover/dev.env

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

58 Commits
 
 
 
 
 
 
 
 

Repository files navigation

dev.env

Developer environment setup. Designed first and foremost to be compatible as a Codespaces dotfiles repo.

Entrypoint: script/bootstrap

Private environment configurations can be added in script/private_environments:

  • This assumes that you have a private repo named ENVIRONMENT_NAME.env.
  • These will only be pulled in on codespaces with the enviornment's ENV_{ENVIRONMENT_NAME}_ACCESS_TOKEN environment variable.
  • The ENV_{ENVIRONMENT_NAME}_ACCESS_TOKEN environment variable must be a GitHub Personal Access Token with read access to the private environment repo.
  • This will execute the environment's script/bootstrap file.

Troubleshooting:

  • ENV_DEV is an environment variable set to the directory where this repo is located on the codespace instance.
  • ENV_{ENVIRONMENT_NAME} is an environment variable set to the directory where the private environment's repo is located on the codespace instance.
  • error.log will be created in ENV_DEV with any errors logged to stderr

You must have coreutils installed to test:

macOS: brew install coreutils

ubuntu: sudo apt-get install coreutils

About

Developer environment setup: compatible as a Codespaces dotfiles repo.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published