-
Notifications
You must be signed in to change notification settings - Fork 206
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
Remove the config supporting running horizon without a captive stellar-core #498
Remove the config supporting running horizon without a captive stellar-core #498
Conversation
nice, horizon's |
I'd rather keep this pull request focused on doing one thing, which is removing the option to control captive. For anyone using captive-core today this change represents a non-functional change, it's 100% refactor and should result in zero side-effects. Changing how captive-core runs would be a functional change and we should keep it separate so that it's easier to tell that the non-functional change is truly non-functional. |
What
Remove the config supporting running horizon without a captive stellar-core. The only way to run horizon will be with a captive stellar-core.
Why
We have two ways to run horizon, with and without captive core. In the quickstart image the default way is without captive core. Outside of the quickstart image the recommended way is with captive core. As far as I can tell we only support the without captive core way in Horizon for backwards compatibility, but it isn't how we want Horizon to be run.
We should run Horizon in quickstart the way we recommend others to run it, by default.
We should remove the option to choose which way to run Horizon because having two ways to run a thing makes maintaining the image harder.