Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some Thoughts about the configuration #120

Open
manuEbg opened this issue Aug 7, 2021 · 0 comments
Open

Some Thoughts about the configuration #120

manuEbg opened this issue Aug 7, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@manuEbg
Copy link
Contributor

manuEbg commented Aug 7, 2021

  • the default config located in our project is called server.config
  • the configs located on the system require the name server.conf
  • the server should report where it is looking for a config
  • the server should report if config was found and read, maybe print the values read from config
  • the jars really should be able to start without a config located on the system
  • after adding a config to my system, testsetup failed without telling me why, because the test server used the config on my system, which included a different port than our default port. This lead to an error during testsetup
  • the server should (at least) check upon read of the config if the omcpath is a valid path
    TODO: make a plan to improve the points above
@manuEbg manuEbg added the bug Something isn't working label Aug 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant