Best practices for working with large repos and other versioning platforms
Choose the recommended Git-based access pattern for your use case:
- For fast read-only access to a XetHub repo, use read-only mount
- For selective read/write access to a subset of files within a XetHub repo, check out lazy cloning
- For read/write access to XetHub from other Git remotes, brush up on Git submodules
- (Deprecated) For read/write access to XetHub from GitHub, install the XetData GitHub app
For non-Git access, explore our advanced Python, CLI, and S3-compatible access patterns.
📄️ Read-only mount
Working with large files often requires significant download times or custom code to handle I/O. When all you want to do is just read what's in a file or repository, there's an easier way. Mount for file system access to a repository, with syntax that works the same both locally and on remote servers.
📄️ Lazy clone
Some Git concepts like cloning don't always make sense for working with large repositories, especially when you only need to interact with a small set of files. To make it easier to develop with large repositories without having to download every file, we built lazy clone.
📄️ Git submodules
If you want to work on a project that combines your existing Git-versioned code and a XetHub asset repo, leveraging Git submodules can streamline your workflow.
📄️ (Deprecated) GitHub app
Add Xet-backed storage to an existing GitHub repository.