install instructions for local install

[pceBuildMaster]

This is a question issue.

I am new to watson and crick so pardon the possible lack of info I know I have.

A possible main issue seems to be the pre-reqs for running crick are not given.

For example yarn. Trying to see if this cmd is installed Ubuntu 18.04 gives the hint:

# yarn
Command 'yarn' not found, but can be installed with:
apt install cmdtest

A bit more research and I know the correct yarn cmd comes from: https://classic.yarnpkg.com/en/

Also the current install step seem to assume user has prior knowledge on things like react, go, auth0 but no solid clues on how to obtain this needed info.

For example once the web front-end is up how does one get the API token to connect to it? Going to https://crick.dev:3000 (after dns config for .dev) one gets a Secure Connection Failed.

From the install steps I see I need to define the CRICK_API_TOKEN:
$ CRICK_API_TOKEN='mytoken' python3 api/scripts/watson_push.py (-h)

I know I am complaining but I am trying to give concrete examples. I am more than willing to do more research AND update the install steps with a pull request once I understand them.

I have researched time tracker apps and watson/crick seem well suited to what my team needs. Not sure one should need to be an expert in all the technologies used by crick to bring it up in a local environment.

Again be glad to give back and improve the install steps if I can get some clues on how to install it.

[jmaupetit]

We are deeply sorry if the base documentation is not straightforward, your feedback is gold to us. 🙏

For example once the web front-end is up how does one get the API token to connect to it? Going to https://crick.dev:3000 (after dns config for .dev) one gets a Secure Connection Failed.

Your local server does not provide an SSL certificate, hence you must use the http protocol instead of https.

Feel free to ask any further questions. Your PR on the documentation would be warmly welcome.

[rzetzsche]

@pceBuildMaster the biggest problem is that .dev tld was bought by google and will be forced per default to https.

You have to disable that in order to access crick.dev per http.
https://stackoverflow.com/questions/47768289/chrome-redirects-dev-to-https