Skip to content

Instantly share code, notes, and snippets.

@coyotte508

coyotte508/upgrading.md

Created August 6, 2018 19:54
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save coyotte508/132779d395ace98c0214372da25a4a35 to your computer and use it in GitHub Desktop.
Save coyotte508/132779d395ace98c0214372da25a4a35 to your computer and use it in GitHub Desktop.
Download ZIP
Upgrading
Raw
upgrading.md

When doing a fresh install, yarn takes the latest versions of the packages according to semver.

Then it creates a yarn.lock file, and won't upgrade the packages anymore.

Yarn upgrade only upgrades the modules installed locally. It has no effect for anybody else as it does not modify package.json.

Upgrading gaia-engine on the website

Option 1

  • Publish gaia-engine
  • Then log on remotely, do cd gaia-site && yarn upgrade @gaia-project/engine

Option 2

  • Publish gaia-engine
  • On the github repo of gaia-site, edit package.json with the most recent version of gaia-engine
  • log on remotely, do cd gaia-site && git pull && yarn install

Upgrading gaia-viewer on the website

Option 1

  • Publish gaia-viewer
  • Then log on remotely, do cd gaia-site/front && yarn upgrade @gaia-project/viewer && yarn build

Option 2

  • Publish gaia-viewer
  • On the github repo of gaia-site, edit front/package.json with the most recent version of gaia-viewer
  • log on remotely, do cd gaia-site && git pull && cd front && yarn install && yarn build

Upgrading the website

For a full upgrade based on the code source of the website, do:

  • log on remotely
  • do cd gaia-site && git pull && yarn install
  • do cd front && yarn install && yarn build

It should update everything, backend & front-end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment