Nas Villanueva
dbf9741b99
Updated urls to use docker compose links
|
%!s(int64=9) %!d(string=hai) anos | |
|---|---|---|
| .gitignore | %!s(int64=9) %!d(string=hai) anos | |
| README.md | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin-clouddev.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin-dev.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin-devoracle.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin-prod.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin-staging.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin-uat.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-admin.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-discovery-staging.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-reg-dev.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-reg-devoracle.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-reg-prod.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-reg-staging.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-reg-uat.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-reg.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-ui-dev.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-ui-staging.yml | %!s(int64=9) %!d(string=hai) anos | |
| crss-ui.yml | %!s(int64=9) %!d(string=hai) anos |
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:
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.
Spring profile To load a spring profile: -Dspring.cloud.config.profile=
There should also be a corresponding file in the git repository with the format -.yml