The installation instruction in README is incomplete.

[4silvertooth]

Clone the Repository
git clone https://github.com/pneumatic/pneumaticworkflow.git
cd pneumatic-workflow

What is supposed to be done after that?
Running npm install in web-client throws errors too.

[pneumojoseph]

@4silvertooth Instruction for deployment via docker in progress

[izak-fisher]

@4silvertooth
clone the repo, checkout into the installation branch(git checkout installation) and then follow the instructions on this wiki page:
https://github.com/pneumaticapp/pneumaticworkflow/wiki/Running-Pneumatic-Locally
I haven't done a 'deep dive' yet but it seems to 'mostly' work (there's a 'known issues' section on the wiki page)

[ejhawkins]

I’m running to a similar bug, I was unable to find the installation branch. Is it quite possible to revert back to 2.0.1 while development is happening on the latest build still. I'm going to try that. Wish me luck!

[mikhail-pokryshchenko-mgs]

After following the manual to run the application in Docker, the containers start successfully, and the application ports is accessible externally. However, when accessing it via a browser, a Bad Request (400) error is returned.

[sarveshshingare]

Is there anyway to locally run only frontend without backed?
Like npm run dev?

[izak-fisher]

The installation instructions in the readme have been updated.
There's no installation branch now, just use the master branch
Once all the containers are up and running on your server, edit the host file on every client machine you plan to be accessing your instance of Pneumatic from like so:

your_server_address pneumatic.local

your_server_address api.pneumatic.local

your_server_address form.pneumatic.local

your_server_address can be either ip or your server's domain name
It seems to work in the sense that I've managed to install and run it on a google cloud instance and then access it from my local machine. I used the google instance's IP address (you also need to allow external connections in your cloud setup)

[izak-fisher]

Is there anyway to locally run only frontend without backed? Like npm run dev?

I haven't tried it, but it would appear that the frontend and backend are closely integrated and if there is no backend up and running where the frontend expects it to be, the frontend will be erroring out all the time