Versions Compared

Old Version 5

changes.mady.by.user Dan King

Saved on

compared with

New Version 6

changes.mady.by.user Dan King

Saved on

Key

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

...

See also EAS Issue 251: Create deployment workaround for TLS 1.2 compatibility problem

Step-by-step workaround for SF-*-WEB servers (e.g. SF-QA-WEB)

(Note: steps for DB and GEO servers are slightly different and will be published as/when needed.)

1. Manually download required files to a computer that has FTP access to the EAS servers

...

3. Connect to relevant server and browse to /var/tmp


  cd /var/tmp


4. Change permissions of shell scripts


  sudo chmod u+x *.sh

5. Move shell scripts to correct location


  sudo cp deploy_eas_init.sh /var/www/html
  sudo cp deploy_eas_source.py /var/www/html
  sudo cp deploy_eas.sh /var/www/html
  sudo cp set_eas_mode.sh /var/www/html
  sudo cp set_eas_env.sh /var/www/html

(warning) Leave the 3 repository folders in /var/tmp/

6. Run the deployment script as sudo


  cd /var/www/html
  sudo ./deploy_eas_init.sh <EAS_COMMIT> <CONFIG_COMMIT> <BITBUCKET_USER>


For example,


  sudo ./deploy_eas_init.sh caaed66 ff939b9 dan-king


7. Confirm deployment with tests

...