Fauna installation fails for some users who don't run `npm install` inside of `/chateau`

[kairstenfay]

@ebaberga and I were just troubleshooting a fauna install.

She was getting the following error when running npm run chateau from the fauna directory.

We couldn't get the server to run until she ran cd chateau && npm install.

What would cause this? Why did this happen? I just did a re-install of fauna on Ubuntu and did not run into this issue.

[jameshadfield]

@kairstenfay @ebaberga can you please change the README for this? chateau is a submodule and has its own npm dependencies -- see https://github.com/nextstrain/chateau/blob/58fe2d308d0f50157d7148eab78be83cb53b65fb/package.json -- so you need to cd chateau; npm install

Additional README modifications:

• after git clone https://github.com/nextstrain/fauna.git one needs to cd fauna

I just did a re-install of fauna on Ubuntu and did not run into this issue.

Hmm. You may have those libraries already (globally?) installed which node can source without needing to reinstall.

[kairstenfay]

Done with two new commits to master by @ebaberga .

~This repo has some unusual restrictions on pushing branches and force-pushing which is why the changes were done via direct commits to master. Feel free to rebase as you see fit @jameshadfield.~

I was mistaken. The issue had something to do with ssh-authentication error on the development side that didn't allow new branches to be created.

[jameshadfield]

Thanks @ebaberga 🎉