Alpaca Eureka Configuration
This guide details all configurations that are available within the Alpaca Eureka. All configurations can be used in
the application-prod.yml file located in the /etc/alpaca/eureka/config
.
Any changes made while Eureka is running will not take effect until after a restart. Use the following command to
restart Eureka - service alpaca-eureka restart
.
YAML (YAML Ain't Markup Language)
All Alpaca configurations are in the YAML (.yml) format.
Basic Rules
- YAML is case sensitive.
- YAML does not allow the use of tabs. Spaces are used instead as tabs are not universally supported.
-
A dictionary is represented in a simple
key: value
form (the colon must be followed by a space):alpaca: migration: announcementRepositoryUsername: "BoNjOuRlEsAmIs049" announcementRepositoryPassword: "viveLEROILouis14" htmlEncodeExports: true
-
All members of a list are lines beginning at the same indentation level starting with a
-
(a dash and a space):broadworks: profileServer: - cluster: Production fileRepo: ProfileServer username: fileadmin password: P@ssw0rd - cluster: Lab fileRepo: ProfileServer username: fileadmin password: P@ssw0rd
-
Comments are denoted by
#
.# Alpaca Configuration alpaca: # Migration Configuration migration: announcementRepositoryUsername: "BoNjOuRlEsAmIs049" announcementRepositoryPassword: "viveLEROILouis14" htmlEncodeExports: true
Full Documentation
Complete YAML documentation can be found here.
Example Configuration
This sample configuration is meant as a guide only. Do not copy and paste the entire content into your configuration.
server:
port: 8761
eureka:
instance:
hostname: alpaca-1.lab.ecg.co
client:
registerWithEureka: true
fetchRegistry: false
logging:
file:
path: /var/log/alpaca
Server (server)
-
port
: The TCP port on which to run the Eureka server.
Eureka (eureka)
-
instance.hostname
: This is a comma separated list of additional Eureka URLs to register with. This allows clustering of Eureka nodes for service discovery. -
client.registerWithEureka
- Indicates whether or not this instance should register its information with eureka server for discovery by others. This defaults to true. -
client.fetchRegistry
- Controls whether or not this client is going to try to connect to the Eureka server(s) in order to download the information on other services' endpoint. It can do so without registering itself. Defaults to false.
Logging (logging)
-
file.path
: The location to write the gateway log. This defaults to/var/log/alpaca
. Rotation and file naming are configured in thelogback-spring.xml
file.