-
Notifications
You must be signed in to change notification settings - Fork 75
[ETCM-121] Refactor configs #681
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
Conversation
7329ff7
to
b013bc7
Compare
baedddd
to
3d2893b
Compare
I think is the way to go =) great job! |
3d2893b
to
8b03317
Compare
please update the README -> https://github.com/input-output-hk/mantis#command-line-version |
@@ -0,0 +1 @@ | |||
{ include "base-chain.conf"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need base-chain
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was created as etc and eth networks share a lot of common configuration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but base == etc. In my opinion, we don't need it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm I'm also a bit on Michal's side in can be a bit confusing
In my opinion I'd just replicate the duplicated configuration in both etc-chain.conf and eth-chain.conf, just to have to check a single file to see all the configurations of a chain. This kinds of files will rarely be touched so I don't see that being too much of a problem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go for it then!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just updated them! Please check that I haven't screwed up in the middle
I noticed some ropsten configuration wasn't properly configured but I'd leave it as is to not fall down in that rabbit hole, if we ever start providing official support for it (seems to be the intent eventually) we'll fix it then
src/universal/conf/app.conf
Outdated
http { | ||
mode = "https" | ||
|
||
certificate-keystore-path = "conf/mantis.jks" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should HTTPS be pre-configured with these values or disabled by default so user can configure it on its own?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Imo for now I'd just disable it and have the user configure it on its own, we can later add it for development's purposes or provide some guide on to how the user should configure it
Misclick 😅 |
@kapke, according to your last comment, maybe the generic script will be enough?
|
@mmrozek I'm not sure. There are 2 issues in that approach:
|
Maybe it's better than nothing to have the script that Michal mentioned? (maybe we could name it mantis-app or mantis-launcher). We could add the .bat version in a separate PR. The other alternative is just removing this script, is it used by any for now? |
…auncher; removed unnecessary configurations from testnet internal; removed https from app.conf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
@@ -0,0 +1,10 @@ | |||
#!/bin/bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't have execute
permission
|
||
# Custom genesis JSON file path | ||
# null value indicates using default genesis definition that matches the main network | ||
custom-genesis-file = null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor: should we maybe get rid of optional genesis path? (separate task for Piotr or Adiran maybe?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally! Here's the task for that: https://jira.iohk.io/browse/ETCM-128
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
Different changes with the objectives of:
Important Changes Introduced
Up-to-discussion
Testing