===============================================================================
 DEPLOY / UPGRADE NOTES  -  SHRDBMS React backoffice
 For whoever packages this folder into an installer, or upgrades a server.
===============================================================================

THE RULE
  A new build is meant to be copied OVER the installed folder.
  Do NOT empty or delete the install folder first.


IIS ALIAS
-------------------------------------------------------------------------------
  Host this folder as an IIS application whose alias is EXACTLY  shrdbms2
  (http://<server>/shrdbms2/). The build bakes /shrdbms2/ into index.html, so a
  different alias loads the page but 404s every script and style (blank page).


WHAT BELONGS TO THE BROKER  -  the  customize\  folder
-------------------------------------------------------------------------------
  Everything the broker edits or drops lives in ONE folder, customize\ :

      customize\branding-config.json   look + sign-in wording
      customize\app-config.js          where the backend is
      customize\favicon.ico            the broker's tab icon
      customize\client-logo\           the broker's logo
      customize\login-images\          the broker's sign-in pictures

  This build ships ONLY the folder, a guide (customize\README.txt,
  branding-config.help.txt) and two templates (branding-config.sample.json,
  app-config.sample.js). It never contains the broker's own files above - that
  is what makes an upgrade safe: there is nothing here to overwrite them with.
  If you build an installer from this folder, keep it that way: overwrite-only,
  never "clean" the folder, never delete anything inside customize\.


FRESH INSTALL
-------------------------------------------------------------------------------
  Nothing to configure. With no customize\branding-config.json the app uses its
  built-in default look (theme-07), and with no app-config.js it uses the backend
  path baked into the build (normally /shrdbms). A 404 for app-config.js in the
  browser console is expected and harmless.
  To customise, the broker follows customize\README.txt.


EVERYTHING ELSE  (index.html, assets/, fonts/, web.config, stansoft-logo/ ...)
-------------------------------------------------------------------------------
  Ours. Replaced by every build - do not hand-edit it.


UPGRADING A SERVER THAT RUNS A BUILD OLDER THAN THIS ONE
-------------------------------------------------------------------------------
  Older builds kept the broker's files next to index.html instead of in
  customize\ :
      branding-config.json   app-config.js   favicon.ico   logos\   images\login\
  They are STILL READ from there (a copy inside customize\ wins), so nothing
  needs moving. Those builds shipped some of them under their real names and the
  broker edited them; this build no longer carries them, so a plain copy-over
  leaves the broker's versions alone. But an installer that CLEARS the folder
  first would delete them - so, once, before the first upgrade, back up the five
  items above (and the whole customize\ folder, if there is one) and put them
  back if anything is missing afterwards.
===============================================================================
