zware/JFrog-Cloud-Installers
1
0
Fork 0
mirror of https://github.com/ZwareBear/JFrog-Cloud-Installers.git synced 2026-01-21 03:06:57 -06:00
Code Issues Packages Projects Releases Wiki Activity

7.7.3 (#39)

Browse Source 
* ARM templates - 7.7.3 support added. Pro and JCR

* ARM templates - Xray 3.8.2 support

* ARM templates - Nginx configuration changed for JCR

* ARM templates - Xray ARM extension script, yq added, Rabbitmq default password added

* ARM templates - Xray, Extension script changes

* ARM templates - RT readme updated, branch for extensions scripts switched back to master

* ARM templates - JCR, updated API, best practives

* ARM templates - Nginx configuration changed for JCR

* ARM templates - MP submissions, Xray installation script changes, master key minimun char number added in JCR

* ARM templates - Parameters draft
This commit is contained in:
Daniel Miakotkin
2020-09-08 13:35:04 -07:00
committed by GitHub
parent 31a0a8b830
commit d56935b274
25 changed files with 185 additions and 492 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
AzureResourceManager/Artifactory/README.md
View File

@@ -50,12 +50,11 @@ considering you have SSL certificate for `*.jfrog.team`
### Steps to upgrade Artifactory Version
1. Login into Primary VM instance and sudo as root. Use the admin credentials provided in the install setup.
1. Login into first member VM instance and sudo as root. Use the admin credentials provided in the install setup.
Note: Use load balancer's NAT entries under Azure resources, to get the allocated NAT port for accessing the VM instance.
2. Stop nginx and artifactory services.
```
service nginx stop
service artifactory stop
```
@@ -67,9 +66,9 @@ Note: Use load balancer's NAT entries under Azure resources, to get the allocate
4. Start artifactory and nginx services.
```
service artifactory start
service nginx start
```
5. Repeat above steps for all member nodes.
5. Repeat above steps for all member nodes then for primary node.
6. To check the version of each node, open Administration -> Monitoring -> Service status
------
#### Note: