Explain one thing at a time from start to finish about a11ywatch HOT 5 CLOSED

I do appreciate your quick responses, but this is very frustrating.

I'm trying this on a Mac & on Ubuntu. Neither has success.

The documentation still isn't clear with Docker or Node.

from a11ywatch.

@mgifford Hi Mike you can use the --help command to see what is available. The --upgrade flag is only available in the build command. I am not sure where the mix up of commands are coming from since the docs show what can be done.

a11ywatch build setups the project contents for the CLI and ability to store runs etc.
a11ywatch build --upgrade is to clear the docker images or local re-installs .

a11ywatch start runs the instance.
a11ywatch stop shuts the instance down.

If you need help on generic issues, the CLI error messages will declare what can or cannot be done.

Example getting command help a11ywatch crawl --help.

from a11ywatch.

If theres any issue with the docs and showing incorrect commands let me know and I can re-open @mgifford thanks!

from a11ywatch.

@mgifford actually looks like --start is available on the a11ywatch start command. Can you run the command a11ywatch -V to show what version you are on? Interesting since the GitHub actions are working and the builds are based across both Mac and Linux.

from a11ywatch.

@mgifford I see that you are using npm to install the project and cargo in another area. Both are separate package managers and the versions are different (atm). It looks like the npm package was outdated and possibly the issue with missing that flag. The latest for the CLI is 0.8.21, feel free to add anything you find to the docs in a PR. We use rust-to-npm for the nodejs install and need put the CLI deploys with CI to avoid missing version bumps ( On our TODO: the CLI was not updating often so it was moved to the side ).

The project is not just a nodejs application and uses many native deps and binaries, this makes it critical to understand the steps, machine specs, and etc in order to debug.

The docs seem to have been stale a bit due to a deployment bug as well.

from a11ywatch.