Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Since the new oms-central-frontend some changes to the frontend development workflow have been made. I will try on this page to gather all relevant information about how frontend development works now, highlighting the new changes.


Purpose

The central does several things

  • Checking which microservices currently are registered and which dependencies they have based on their getModules.json
  • npm install all dependencies and concatenate them into optimized vendor.js and vendor.css files.
  • download and concatenate all css and js files from the microservices into optimized main.js and main.css files.
  • Create the html basis of the page, which includes the menu and some other things which are common to the whole frontend.
  • Serve everything on /


CLI Usage

You will want to interact with the central frontend when developping. 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 

  • No labels