Home Esplora Aiuto
Registrati Accedi
crssadmin
/
crssconfig
1
0
Forka 0
File Problemi 0 Pull Requests 0 Wiki

Nessuna descrizione

Albero (Tree): 15151fd577
Rami (Branch) Tag
crssconfig
ZIP TAR.GZ
Julius Cessar Lapugot 15151fd577 [BCQ] Add query for saving special event 9 anni fa
crss-admin ebe154f6a6 Add esignature config 9 anni fa
crss-metering 15151fd577 [BCQ] Add query for saving special event 9 anni fa
crss-reg 0c95ea2c1e Fix port used in staging. 9 anni fa
crss-sched 2857f12266 Lower hikari pool config for scheduler service 9 anni fa
crss-ui b07478784e Add pemc-staging profile 9 anni fa
.gitignore 07d2f1ea8b Updated gitignore 9 anni fa
README.md 968c20c111 Test commit. 9 anni fa
application.yml d96ba13dc3 Update uat graylog host 9 anni fa

README.md

NOTES:

Default config should be for the current deployment environment (e.g. Staging or Production). The reason being, it should not require additional command line config to run the services. Developers should instead specify the additional command line config when executing the services.

These are the options for the developers:

  1. git branch Spring Cloud Config is able to handle git branches. This config is ideal if you have config experimentation and don't want to impact other developers. Specify -Dspring.cloud.config.label= when running the service.

  2. Spring profile To load a spring profile: -Dspring.cloud.config.profile=

    3. There should also be a corresponding file in the git repository with the format -.yml