It would be good if the docs and --help output could mention that nvm install installs and uses the given Node version. I've probably wasted hours typing nvm install __ && nvm use __, - just discovered the second part has been unnecessary since this was fixed in 2014 :)

There's a section about Uninstall existing npm, but the recommendations for upgrading are scattered in the issues.

The relationship between node, npm and nvm is not clear and it's not obvious if upgrading npm should be done through nvm or at least in a way that doesn't break nvm.

There is no mention of the --fish option in the README and its functionality is encapsulated by the --shell option, but --fish is still documented in the manpage and still works.

After the most recent fish shell update on Ubuntu, fish loses the ability to find node / nvm. I get the following message on opening terminal.

~/.local/share/omf/pkg/nvm/init.fish (line 10): Expected a string, but instead found a '&'
    fenv source $nvm_prefix/nvm.sh >/dev/null ^&1
                                               ^
from sourcing file ~/.local/share/omf/pkg/nvm/init.

Over at https://gitter.im/publiclab/publiclab?at=5c0d471df992693c7a4913e2 I hear there are many undocumented behaviors. We should add them to the README.

Description

I've configured crontab as per documentation, but when I'm trying to connect to any SSH inside my cron job it fails on access denied (public key) error.

Steps to reproduce:

1. touch ./docksal/services/cli/crontab
2. Add following to recently created file:

   * * * * * bash -lc 'env >> /tmp/cron-test.log 2>&1'