* * WEB Server
Also see the following Bitbucket issues:
- EAS-251 : Create deployment workaround for TLS 1.2 compatibility problem
- EAS-254 : Create an automated deployment workaround for TLS 1.2 compatibility problem
Step-by-step workaround for <environment>_WEB servers (e.g. SF_QA_WEB)
Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, SD_PROD
1. Manually download required files to a computer that has FTP access to the EAS servers
A. Download Repositories
There are three EAS repositories to download.
The names of the repository folders are important. It is recommended that the repositories be download by using a Web browser in the downloads section of each repository. It is important to accept the default name for the downloaded folders.
Tags Tab
The Tags tab will let you select which changeset, and format, that you want to download.
Mercurial:
1. https://bitbucket.org/sfgovdt/eas/downloads/?tab=tags
2. https://bitbucket.org/sfgovdt/sfeas_config/downloads/?tab=tags
3. https://bitbucket.org/sfgovdt/thirdparty/downloads/?tab=tags
Git:
1. https://bitbucket.org/sfgovdt/easx/downloads/?tab=tags
2. https://bitbucket.org/sfgovdt/easconfigxsf/downloads/?tab=tags
3. https://bitbucket.org/sfgovdt/thirdpartyx/downloads/?tab=tags
Unzip the three downloaded zip files.
Extract the contents of each unzipped folder.
Example folder names
Mercurial:
sfgovdt-eas-caaed66d58b3
sfgovdt-sfeas_config-ff939b913451
sfgovdt-thirdparty-8a1b00afcb15
Git:
sfgovdt-easx-7a7a6ad72b0f
sfgovdt-easconfigxsf-bd73cd53771c
sfgovdt-thirdpartyx-08f69eb30d1a
Again, the folder names are important, so do not change them.
B. Download Workaround Deployment Scripts
Download the latest version of these five files from the /eas/web/bin/ source folder.
Mercurial: https://bitbucket.org/sfgovdt/eas/src/default/web/bin/
Git: https://bitbucket.org/sfgovdt/easx/src/master/web/bin/
1. deploy_eas_init.sh
2. deploy_eas_source.py
3. deploy_eas.sh
4. set_eas_mode.sh
5. set_eas_env.sh
2. FTP the 3 folders and 5 files to the /var/tmp folder of the server(s) to be deployed
Example of uploading the files from Windows to the /var/tmp directory of the target server using FTP tool FileZilla (via Mercurial):
See also https://filezilla-project.org/
See also PuTTY and SSH
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 their correct locations
sudo cp deploy_eas_init.sh /var/www/html |
Leave the 3 repository folders in the directory /var/tmp/
6. Run the deployment script as sudo
cd /var/www/html |
For example,
sudo ./deploy_eas_init.sh caaed66 ff939b9 dan-king |
7. Confirm deployment with tests
The deployment can be confirmed by performing the steps that are described in Section 3 of the Testing page.
Related articles