Stellar developer docs for Galexie #1072
Conversation
|
Something went wrong with PR preview build please check |
urvisavla
force-pushed
the
galexie-docs
branch
from
c12b7aa
to
dff6e82
Compare
|
Something went wrong with PR preview build please check |
urvisavla
force-pushed
the
galexie-docs
branch
from
dff6e82
to
0f28006
Compare
|
Something went wrong with PR preview build please check |
urvisavla
force-pushed
the
galexie-docs
branch
from
0f28006
to
041aaa6
Compare
|
Preview is available here: |
urvisavla
force-pushed
the
galexie-docs
branch
from
041aaa6
to
1c78a33
Compare
|
Something went wrong with PR preview build please check |
urvisavla
force-pushed
the
galexie-docs
branch
from
1c78a33
to
ddfcac5
Compare
|
Preview is available here: |
urvisavla
force-pushed
the
galexie-docs
branch
from
ddfcac5
to
c1270f3
Compare
|
Preview is available here: |
urvisavla
force-pushed
the
galexie-docs
branch
from
c1270f3
to
af812bc
Compare
|
Preview is available here: |
urvisavla
force-pushed
the
galexie-docs
branch
from
af812bc
to
62e93e5
Compare
|
Preview is available here: |
|
We can maybe fix this in another PR, but I think it would be helpful if on the Data Overview page we list all the services in the same order. Example: RPC And then do this for the sidebar, for the descriptions, in the table, the links, etc. It's kind of confusing when they're in a different order everywhere! |
| sidebar_position: 30 | ||
| --- | ||
|
|
||
| # Installing |
There was a problem hiding this comment.
Should we add a link to the github readme instructions for installing/building locally?
There was a problem hiding this comment.
Good point. I don't think we currently have instructions for building it locally but it might be worth adding them.
Co-authored-by: chowbao <[email protected]>
|
Preview is available here: |
Co-authored-by: chowbao <[email protected]>
|
Preview is available here: |
|
Something went wrong with PR preview build please check |
|
Preview is available here: |
|
|
||
| The append command maintains strict sequential integrity within each export session. If interrupted and then restarted with the same range, it automatically resumes from where it left off before interruption, ensuring no ledgers are missed within a session. | ||
|
|
||
| ### Scan-and-fill Command |
There was a problem hiding this comment.
Would it make sense to add like a (Recovery mode) or equivalent here further emphasizing that scan-and-fill isn't normal usage
@briwylde08 I've adjusted the order. Please let me know if I missed anywhere. |
Co-authored-by: chowbao <[email protected]>
|
Preview is available here: |
|
Preview is available here: |
|
Preview is available here: |
* Stellar developer docs for Galexie * Refine CLI section based on review feedback. Add monitoring section. * Fix order of services in Data section * Update docs/data/galexie/admin_guide/monitoring.mdx * Add hardware requirements section * Remove reference to Grafana Dashboard.
Addresses #1012