-
Notifications
You must be signed in to change notification settings - Fork 225
Description
What problem does your feature solve?
The quickstart image does not include a galexie meta lake. When building solutions that intend to work with a mainnet meta lake generated with galexie, it is difficult to test against any sort of small local network since quickstart does not support it today.
What would you like to see?
Add galexie to quickstart, have it publish a meta lake inside quickstart and serve that meta lake in a similar / same way that the history archive is served in quickstart.
It could be an optional service.
Challenges
Because galexie creates many files, it may not be practical to do this on a long running quickstart. Quickstart already publishes a local history archive that grows forever, so it isn't expected to run forever. But maybe if this significantly shortens the life of a quickstart it means making it optional for non-local network setups. Or maybe there's a way that galexie could only create files for non-empty ledgers, since a lot of ledgers on quickstart are empty.
What alternatives are there?
Folks run galexie manually outside quickstart.
cc @stellar/platform-eng
Metadata
Metadata
Assignees
Labels
Type
Projects
Status