Where to store global enterprise properties?
I’m faced with a crowd of java applications, which need different global enterprise wide properties for operation, for example: hostname of the central RDBMS, hostname and location of the central self-service portal, host location of central LDAP, host location of central mail server etc.
Where to store global enterprise properties?
I’m faced with a crowd of java applications, which need different global enterprise wide properties for operation, for example: hostname of the central RDBMS, hostname and location of the central self-service portal, host location of central LDAP, host location of central mail server etc.
Which approach would be better for persisting these overridable configuration keys and values? A simple key-value store, or a graph database?
I’m creating a system where there are config keys and values. So for example:
Which approach would be better for persisting these overridable configuration keys and values? A simple key-value store, or a graph database?
I’m creating a system where there are config keys and values. So for example:
Developing configuration syntax – best practise/rules/methods?
I am currently developing a small application, which checks if provided data meets certain requirements. The requirements are actually a long list, and might be changing, so I defined a syntax which allows me to state all of the requirements briefly and in a seperate file.
Developing configuration syntax – best practise/rules/methods?
I am currently developing a small application, which checks if provided data meets certain requirements. The requirements are actually a long list, and might be changing, so I defined a syntax which allows me to state all of the requirements briefly and in a seperate file.
Developing configuration syntax – best practise/rules/methods?
I am currently developing a small application, which checks if provided data meets certain requirements. The requirements are actually a long list, and might be changing, so I defined a syntax which allows me to state all of the requirements briefly and in a seperate file.
Project configs for Java projects
How to store configs for project in Java. In normally case i stored it in ‘src/main/resources/’ with *.properties. How best approach for storing projects config for development, local, production environments?
Project configs for Java projects
How to store configs for project in Java. In normally case i stored it in ‘src/main/resources/’ with *.properties. How best approach for storing projects config for development, local, production environments?
What should config files and the bootstrap do? [closed]
Closed 9 years ago.