| Table of Contents |
|---|
Step-by-step workaround for
...
* * GEO
...
Servers (e.g. SF_QA_GEO)
Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, DR_PROD
Contents:
| Table of Contents |
|---|
Part 1. Manually download required files to a computer that has FTP access to the EAS servers
1.A. Download
...
Repository
There is one EAS repository to download.
...
1.A.1. Visit the download page of the repository
Mercurial -https://bitbucket.org/sfgovdt/sfeas_config/downloads/?tab=tags
Git - https://bitbucket.org/sfgovdt/easconfigxsf/downloads/?tab=tags
1.A.2. Download the .zip file from the most recent branch
The downloaded compressed files will be named something like this (Mercurial):sfgovdt-sfeas_config-ff939b913451.zip
or this (Git):
sfgovdt-easconfigxsf-fcf152a4111f.zip
1.A.3. Uncompress the zip file.
This will result in three folders, such as this:sfgovdt-sfeas_config-ff939b913451
Uncompress the zip file.
| Note |
|---|
Again, the folder name is important, so do not change it. |
Example of downloaded repository names in Windows:
...
1.B. Download Workaround Deployment Scripts
1.B.1 Download the latest version of these 4 files.
Download from the /eas/geoserver/ source folder at
Mercurial - https://bitbucket.org/sfgovdt/eas/src/default/geoserver/
Git - https://bitbucket.org/sfgovdt/easx/src/master/geoserver/
Tip: Navigate to the workaround deployment script file in the repository with a browser on the target machine, invoke the "... → Open raw" menu command, and then save the file in the directory that is specified below.
...
From the config/web/settings_env/live/ source folder at
Mercurial - https://bitbucket.org/sfgovdt/sfeas_config/src/default/web/settings_env/live/
Git - https://bitbucket.org/sfgovdt/easconfigxsf/src/master/web/settings_env/live/
4. environments.py
Part 2. FTP the 1 folder and 4 files to the /var/tmp folder of the server to be deployed
...