GitLab vs Google Drive sync — choosing the right path in Lattuce
Compare GitLab Notes sync, Google Drive Library sync, and storage options in Lattuce. Choose the right setup for notes, PDFs, and portable files.
Choose GitLab for a portable Markdown copy of a Notes folder. Choose Google Drive to bring documents into your Library and refresh sources from a Drive folder. You can use both in the same research workflow on lattuce.app.
For researchers and authors, the useful question is what needs to stay in sync: your own notes, the documents you read, or the files behind your account. Lattuce handles these through different connections.
| Your goal | Lattuce option | What it does |
|---|---|---|
| Keep notes as readable Markdown in a repository | GitLab vault sync | Exchanges a selected Notes folder and its descendants with a repository subdirectory |
| Use an existing Drive document as research material | Google Drive Library import | Adds an individual file as a Library source |
| Keep Library sources aligned with a Drive folder | Google Drive folder sync | Refreshes sources from that folder, using mirror or reference mode |
| Choose where source files and attachments are stored | Bring Your Own Storage, where enabled | Uses a configured storage backend for file bytes |
| Start writing without connecting another service | Managed Lattuce storage | Provides the default account storage path |
These connections depend on the features enabled for your account and installation. Start with the options visible in your settings; a provider account alone does not enable an integration.
Before you start
Decide which material you want to connect, and have access to its destination.
- For GitLab: a Notes folder, access to a GitLab repository, a branch, and a dedicated subdirectory within that repository.
- For Google Drive: access to the file or folder, an available Google Drive connection in Library, and permission to connect it.
- For BYOS: an enabled storage option and the required access to that backend.
Start with a small folder whose contents you recognize. Confirm where files appear and how updates behave before connecting a larger collection.
1. Choose GitLab when the notes themselves should travel
Suppose your literature review notes belong in a repository alongside your research documentation. GitLab vault sync connects one Lattuce Notes folder, including its descendants, to a chosen branch and subdirectory.
The files are Obsidian-compatible Markdown. Sync works in both directions, so the connection can bring repository changes back into Notes as well as send Notes changes to GitLab.
The designated subdirectory is mandatory; the repository root is not a sync destination. Changes outside that subdirectory are outside this connection's scope. That boundary helps you keep notes alongside other repository material.
GitLab's particular strength is readable change history. Git commits record checkpoints, and GitLab lets you inspect changes between them. That is useful when you need to recover an earlier explanation or review how a note developed. GitLab commit documentation
Open Account settings → GitLab vault sync, select your Notes folder, and configure the repository, branch, and subdirectory. Review the resulting Markdown and sync status after a small edit.
Automatic sync responds to saved changes after a short delay. Treat the reported status as your confirmation that the remote copy is current; saving a note does not guarantee that GitLab has already received it.
2. Choose Google Drive when your reading material lives there
Drive is a natural fit for a lab folder of PDFs, documents, and other supporting files. Its advantage is familiarity: you can keep organizing source material where your collaborators already work.
In Lattuce's Library, the Google Drive panel supports importing an individual file and connecting a folder for ongoing source updates. Folder sync offers two modes:
- Mirror copy: Lattuce stores a copy through its configured file storage backend.
- Stream from Drive (reference): the source points to the original in Drive, while Lattuce still extracts content and may cache data for processing.
Both modes leave the original in Drive. Choose mirror when you want a stored copy for the Library workflow. Choose reference when you want Library to refer to the Drive original rather than maintain a full mirrored file copy. Lattuce still extracts content and may cache data in reference mode.
Use Import file for one document or Sync folder for a small folder. Choose the mode and check that sources become ready. Then update a document, select Sync now, and confirm the Library reflects the change.
If a connected file is removed, moved out of scope, or trashed, its Library source can be marked unavailable. Do not assume that removing a file in Drive deletes every associated record in Lattuce.
Drive folder sync refreshes Library sources from Drive. It is a different workflow from exchanging a Notes folder as Markdown, and does not give Lattuce documents Google Docs-style simultaneous editing.
3. Separate file storage from account sync
Bring Your Own Storage answers where file bytes live. Depending on what is enabled, Lattuce can use Drive or S3-compatible storage for source files and attachments.
Choosing a file backend does not move your identity, account metadata, and every workspace record into that provider. A Drive Library connection and a Drive storage backend also serve different purposes, even though both use Google Drive.
The managed cloud default is enough to start. You do not need a GitLab repository to use Lattuce. Read the BYOS guide alongside your available account settings when storage location becomes a requirement.
4. Check conflicts and recovery before depending on sync
If the same note changes in Lattuce and GitLab, a conflict may need your decision. Conflicts are parked for review, with choices to keep the local version, the GitLab version, or both. This is a review step, not a live coediting promise.
GitLab vault sync covers the selected Notes folder. It should not be treated as a full-account backup or a complete attachment vault. Lattuce's own version history is another recovery feature worth understanding.
Local Notes caching and queued device synchronization are also separate from the GitLab connection. For the available workflows and setup details, see MCP and local sync.
What about Dropbox, OneDrive, Nextcloud, or Syncthing?
Other file tools can help you organize or synchronize ordinary exported files outside Lattuce. That does not make them interchangeable native connections to Notes or Library. Check the integrations and sync guide for supported paths.
A practical research setup can use Drive for shared source documents, GitLab for portable reading notes, and Lattuce for the research-and-writing workflow that connects them. Pick each connection for the material it handles, then verify one complete update before expanding it.