Page Comparison

...

You will want to interact with the central frontend when developing. In general, a rebuild of the frontend can be performed by running bash oms.sh run oms-central-frontend gulp. This will rebuild the frontend to reflect the current status of the services as returned by the serviceregistry. 

• If you just did a couple of small changes in a file that was already included, a gulp rebuild in the oms-central-frontend container might be what you want to do (bash oms.sh run oms-central-frontend gulp)
• (bash oms.sh run oms-central-frontend gulp)
• If you intend to do several changes but not add or remove files, you will not want to run a frontend rebuild every time you change something. For this, the central frontend offers to build the frontend in

...

• dev dev-mode, which turns off most of the code optimisations including concatenating the files into one, and will include your sources directly. To turn on dev mode, change the boolean devMode in oms-central-frontend/lib/config.json to true and run gulp in the oms-central-frontend container. 
• If you added new frontend files or dependencies, you will atm have to restart oms-serviceregistry and rerun the gulp task. A bash oms.sh down && bash oms.sh up -d will do the same thing, but if you don't want to recreate the whole ecosystem you might want to write a script for this.

...