Feature Request

The original version of ws has .once and .activation scripts. Provide a means to add activation scripts to a repo, provide an online list of supported activations.

Problem

Some programming languages require specific environment setup. Examples include:

• Go with GOPATH
• Python with pyenv
• Ruby with rbenv
• Node.js with NPM

Each of these options provide the means to separate and isolate development environments. What better way to manage these than on a per workspace basis.

Proposed Solution

Have users declare a .post-checkout-config.yaml file in their project, and wire this into a post-checkout Git hook.

Having a YAML file and following idioms found in pre-commit satisfy static dependencies (such as updating pip, npm, rb, godeps) but it won't resolve the environment variable issues. The best I can think of to resolve this is to place an activation script into the ws etc directory so that upon workspace refresh it will be picked up.

Implement the hook in simple Python to apply the changes to the workspace as required.

The YAML syntax for the implementation can be simple, such as that used in precommit.

Adding activation hooks is simple as adding a new section to the file.

The implementation can largely be forked from the fantastic pre-commit project.