User Tools
development:applications:mib_manager
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:mib_manager [2023/01/26 15:33] – [Ansible Playbook] 10.91.110.100 | development:applications:mib_manager [2023/01/26 17:58] (current) – [Env Config] 10.91.110.100 | ||
|---|---|---|---|
| Line 16: | Line 16: | ||
| Click edit before copying and pasting (ansible doesnt like something about this text) | Click edit before copying and pasting (ansible doesnt like something about this text) | ||
| - | ansible-playbook -i ../ | + | ansible-playbook -i ../ |
| - | Upload step will upload the back-end spring boot jar and front end angular files. Deploy step will replace the front end and back-end files with the latest upload. Configure will update the application.properties file as found in deployment playbooks. It is best to run configure along with upload and deploy, as the front end configs URL will default to localhost on upload. Running config changes the url to whatever is set as mib_manager_url in the env config vars for that environment. | ||
| ---- | ---- | ||
| Line 30: | Line 29: | ||
| ===== Env Config | ===== Env Config | ||
| - | This app uses the env-configuration repo to get information for sending files to remote hosts. When you login, it will clone the env-config repository onto the server. Any further logins will check for the presence of the env-config folder, | + | This app uses the env-configuration repo to get information for sending files to remote hosts. When you login, it will clone the env-config repository onto the server. Any further logins will check for the presence of the env-config folder, |
| ---- | ---- | ||
development/applications/mib_manager.1674747213.txt.gz · Last modified: 2023/01/26 15:33 by 10.91.110.100
Page Tools
