mirror of
https://seed.radicle.dev/rad:z371PVmDHdjJucejRoRYJcDEvD5pp.git
synced 2026-10-18 19:10:34 +08:00
faq: Update private repositories
This commit is contained in:
committed by
Lorenz Leutgeb
parent
43bb1a1cbf
commit
e954dc9d1d
+6
-7
@@ -107,9 +107,8 @@ We expect more improvements in search/discovery in the future.
|
||||
## Can Radicle handle large binary files like datasets or machine learning models?
|
||||
|
||||
Radicle uses Git internally, which can handle moderately-sized binary data
|
||||
relatively well. For large data however, we are considering adding support for
|
||||
solutions like `git-annex` or `git-lfs`. We intend for Radicle to help with
|
||||
the proliferation of open source AI models.
|
||||
relatively well. For large data however, solutions like `git-annex` or `git-lfs` exist.
|
||||
We intend for Radicle to help with the proliferation of open source AI models.
|
||||
|
||||
## How does Radicle ensure persistence and availability of repositories when nodes go offline?
|
||||
|
||||
@@ -154,10 +153,10 @@ abusive behavior.
|
||||
|
||||
## Is there a way to host private repositories on Radicle?
|
||||
|
||||
Yes, Radicle supports private repositories that are only shared among a trusted
|
||||
set of peers, not the entire network. These are not encrypted at rest but rely
|
||||
on selective replication and are thus completely invisible to the rest of
|
||||
the network.
|
||||
Private repositories should not be used until we have a resolution for the
|
||||
[security vulnerability in the network protocol][vuln].
|
||||
|
||||
[vuln]: {% post_url 2026-09-23-disclosure-of-vulnerability-in-network-protocol %}
|
||||
|
||||
## What is the process for migrating existing GitHub projects to Radicle?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user