Skip to content

Draft: Rework Docker files to build without breaking Git source

Theodore Zorbasrequested to merge
reworkDocker into master
  • Original Git repo is preserved whole in a source subfolder
    • No changes are now made directly to this repo, so can it act as a solid reference to build from
      • Any git command tools will work exactly as they should (e.g. what's being used by the metrologyanalysis to scan git describe)
    • Where there were changes, these have been added to the .gitignore or reworked otherwise to suppress, without any real consequences
    • To get back to not storing the entire Git monorepo in the final Docker image (e.g. "pixel" stuff in a "strips" web app), git sparse-checkout is used to selectively retain which folders are kept without violating Git diff
  • Symlinks are used in userPages and etc to build the web app, by pointing back to the source folder
    • Everything for how the deployment was originally made should be preserved to their original paths this way without any need for hacks, it just works cleanly
  • metrologyanalysis submodule was also updated to v0.1.2

TODO:

  • Deployed only for the Strips app to start with, should expand this to the others as well - but could consider deploy this now for Strips, so testing/observation can be had, before carrying over to others
  • Entire Git repository is preserved in each of the apps as a consequence, but optimisation could be investigated in the form of git sparse-checkout
  • Git diff is still detected on files in commonCode/stageTestList_*.csv, as these are tracked in Git but get changed during build time - would you consider deleting these files from Git tracking if they are just "cache" files getting automatically updated?

Merge request reports