mirror of
https://github.com/logos-storage/logos-storage-docs-obsidian.git
synced 2026-01-02 13:23:08 +00:00
rename: "Team-NLBR Solution Proposal" => "High-Level Solution Proposal"
This commit is contained in:
parent
2cf61aecd8
commit
8b1fc7314b
@ -1,6 +1,6 @@
|
||||
---
|
||||
related-to:
|
||||
- "[[Team-NLBR Solution Proposal]]"
|
||||
- "[[High-Level Solution Proposal]]"
|
||||
- "[[status-go publishing magnet links]]"
|
||||
- "[[status-go processing magnet links]]"
|
||||
- "[[status-go-codex integration - design notes]]"
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
related-to:
|
||||
- "[[Team-NLBR Solution Proposal]]"
|
||||
- "[[High-Level Solution Proposal]]"
|
||||
- "[[status-go publishing magnet links]]"
|
||||
- "[[status-go processing magnet links]]"
|
||||
- "[[status-go-codex integration - design notes]]"
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
related-to:
|
||||
- "[[Team-NLBR Solution Proposal]]"
|
||||
- "[[High-Level Solution Proposal]]"
|
||||
- "[[status-go publishing magnet links]]"
|
||||
- "[[status-go processing magnet links]]"
|
||||
- "[[status-go-codex integration - design notes]]"
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
related-to:
|
||||
- "[[Team-NLBR Solution Proposal]]"
|
||||
- "[[High-Level Solution Proposal]]"
|
||||
- "[[status-go publishing magnet links]]"
|
||||
- "[[status-go processing magnet links]]"
|
||||
- "[[status-go-codex integration - design notes]]"
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
related-to:
|
||||
- "[[Team-NLBR Solution Proposal]]"
|
||||
- "[[High-Level Solution Proposal]]"
|
||||
- "[[status-go publishing magnet links]]"
|
||||
- "[[status-go processing magnet links]]"
|
||||
- "[[status-go-codex integration - design notes]]"
|
||||
@ -11,7 +11,7 @@ The notes in this document aim at recording our path towards the Codex integrati
|
||||
|
||||
## Codex for History Archives
|
||||
|
||||
As indicated in the [[Team-NLBR Solution Proposal]], the central entry point to the history management is [InitHistoryArchiveTasks](https://github.com/status-im/status-go/blob/6322f22783585474803cfc8a6f0a914757d763b5/protocol/messenger_communities.go#L3783). `InitHistoryArchiveTasks` is called from **two main places**:
|
||||
As indicated in the [[High-Level Solution Proposal]], the central entry point to the history management is [InitHistoryArchiveTasks](https://github.com/status-im/status-go/blob/6322f22783585474803cfc8a6f0a914757d763b5/protocol/messenger_communities.go#L3783). `InitHistoryArchiveTasks` is called from **two main places**:
|
||||
- During `Messenger.Start()` (startup)
|
||||
- When enabling archive protocol
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
related-to:
|
||||
- "[[status-go-codex integration - design notes]]"
|
||||
---
|
||||
In [[Running Unit Tests for status-go]] we provide general notes on running unit tests in the status-go project. And then we have a similar note about functional tests in [[Running functional tests in status-go]].
|
||||
In [[Running Unit Tests for status-go]] we provide general notes on running unit tests in the status-go project. And then we have a similar note about functional tests in [[Running functional tests in status-go]].
|
||||
|
||||
Also, to learn the history archive creation/upload and download/processing flows (recorded AI conversation with some edits), please check:
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user