Background
On December 01, 2018 the EAS source code version control provider, Bitbucket, disabled support of TLSv1 and TLSv1.1 and began requiring secure connections through TLS 1.2.
The EAS stack does not currently support TLS 1.2 (as of December 2018). While this issue is being resolved there is a workaround for deploying EAS source code.
See also EAS Issue 251: Create deployment workaround for TLS 1.2 compatibility problem
Step-by-step workaround for * * 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
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.
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
The downloaded compressed files will be named something like these:
sfgovdt-eas-caaed66d58b3.zip
sfgovdt-sfeas_config-ff939b913451.zip
sfgovdt-thirdparty-8a1b00afcb15.zip
Uncompress the files.
This will result in three folders, such as these:
sfgovdt-eas-caaed66d58b3
sfgovdt-sfeas_config-ff939b913451
sfgovdt-thirdparty-8a1b00afcb15
Again, the folder names are important, so do not change them.
Example of downloaded repository folders (compressed and uncompressed) in Windows:
B. Download Workaround Deployment Scripts
Download the latest version of these five files from the /eas/web/bin/ source folder
https://bitbucket.org/sfgovdt/eas/src/default/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:
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
Related articles
Filter by label
There are no items with the selected labels at this time.
0 Comments