...
See also EAS Issue 251: Create deployment workaround for TLS 1.2 compatibility problem
Step-by-step workaround
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 
The names of the repository folders are important. It is recommended that the repositories be download from a web browser , accepting the in the downloads section of each repository. It is important to accept the default name for the downloaded filefolders.
1. https://bitbucket.org/sfgovdt/eas/downloads/
2. https://bitbucket.org/sfgovdt/sfeas_config/downloads/
3. https://bitbucket.org/sfgovdt/thirdparty/downloads/
The downloaded compressed files will look be named something like thisthese:
sfgovdt-eas-caaed66d58b3.tar.gzzip
sfgovdt-sfeas_config-ff939b913451.tar.gzzip
sfgovdt-thirdparty-8a1b00afcb15.tarzip
Uncompress both the 'gz' and 'tar' files (a two-step process in Windows Explorer).
This will result in three folders, such as these:
sfgovdt-eas-caaed66d58b3
sfgovdt-sfeas_config-ff939b913451
sfgovdt-thirdparty-8a1b00afcb15
Again 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 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 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 |
(Leave Leave the 3 repository folders in 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
...
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...