Development Environment Setup¶
The following instructions assume you are working on Linux (or with WSL on Windows) and have conda and vscode.
- Check/install
conda
Check that you have conda installed:
You should see a list of parameters and values, which should include something like the following:
If not, install miniforge3.
-
Download miniforge
-
Run the install script
The interactive installation will prompt you to initialize conda with your shell. Do NOT do this if you are on a SLURM HPC. If you are on your personal computer it should be fine.
TODO-copier-package point to docs for more info.
-
Install the recommended VSCode extensions for this project.:
-
Open the Command Palette: On macOS:
Cmd+Shift+POn Windows/Linux:Ctrl+Shift+P. -
Show recommended extensions: Type and select
> Extensions: Show Recommended Extensions -
Click the Install button for each recommended extension listed above.
-
Create a development environment with conda
# Create the environment (or update and prune if it already exists)
conda env update --name able-workflow-copier --file environment-py312-dev.yaml --prune
conda activate able-workflow-copier
Alternatively, run the script scripts/conda_update.sh.
Configure the able-workflow-copier as the default python environment in the Python Environments VSCode extension.
- Install pre-commit into the repo to run checks on every commit
- Play around in the sandbox. (The
sandbox/directory is in.gitignoreand is a good place to explore how to use the template.)
--trust: Required to run this "untrusted"copiertemplate under development.--vcs-ref HEAD: Use theHEADof the git repo, not a tagged release version.--pretend: Do not modify any files, just ask the questions."./": Thecopier.yamlfile is located in the current directory. When working in production, this will be replaced with the github link toable-workflow-copier."sandbox/example": The directory to place the rendered template, if we were not pretending.