Versions Compared

Old Version 2

changes.mady.by.user Eddie Rubeiz

Saved on

compared with

New Version 3

changes.mady.by.user Eddie Rubeiz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

$CREATE_CMD $SECURITY_OPTS --extra-vars "role=jobs tier=production"

2. Web

$CREATE_CMD $SECURITY_OPTS --extra-vars "role=web tier=production" --extra-vars "@group_vars/

...

kithe_web_production_override"

Switch

  • Point the prod URL in your etc/hosts file locally to the web server.

  • Deploy master branch to all the new servers.

    bundle exec cap production deploy --trace

    (lightbulb)At this stage, if you point the prod URL in your etc/hosts file locally to the web server, you should see a functioning production website.

    (lightbulb)Visiting the workers page should show twice the usual number of workers (as of Aug. 2020, that’s 24 workers).

  • Point elastic IP to the new web server:

    • Select Elastic IPs

    • Select digicoll-production

    • Actions ➡ Associate address

    • Under the "Resource type", Choose "Instance".

    • Fill in the appropriate instance (the new prod web server)

    • Check Allow this Elastic IP address to be reassociated if already attached"

    • Click Associate.

  • Remove the etc/hosts entry and check that traffic is indeed routed to the new server.

  • Spin down the old web and jobs servers.

  • Announce the switch is complete.

...