Share to cloud
Štýl: ~80 % ASD-STE100
verified: 2026-11-01 (rename behavior: HTTP/PostgreSQL and service rescan tests; same-name gate: service and mounted component tests; Share button: component tests and WebKit geometry/colour tests; packaged desktop verification pending).
Publish a local file as a public, view-only link that updates every time you save.
| Term | Meaning |
|---|---|
| Local file | The original document on your computer |
| Cloud copy | The note published from that file |
| Public link | A read-only address for the cloud copy |
How to reach it
Use Share in the editor's header, or Share to cloud in a file's row menu in the sidebar. Once a file is shared, the same places show Copy link and Stop sharing instead. Share to cloud in the sidebar always shares to Personal; to share into an organization, use Share and choose the space.
In the dialog, press the centred Share button. The line below it says Anyone with link can view. After sharing, the same button says Stop sharing. The public link and Copy appear below it.
What sharing does
- The file is published as a note in a Shared local files folder in the cloud space you choose, with a link anyone can open, read-only. The app sends the file's text, its name, its full path on your computer and the local images it uses. The path stays with the note in your cloud space; the public link shows the file name, the text and the time of the last update, not the path.
- Every later save pushes the new content to that note, no matter where the save came from: this app, another editor, a Git commit, or a Raven Sync update all count.
- Sharing is strictly one-way. Nothing ever writes back into the local file from the cloud; there is no pull, no merge, and nothing to reconcile.
- If you clear the file locally, the public page keeps showing the last real content and marks it stale in the app, rather than going blank.
While sharing is on, the text under the link has two paragraphs:
- Saving the local file updates the cloud copy while Context Raven is running and you are signed in.
- Turning sharing off stops this computer's link and deletes the cloud copy. The file on this computer stays.
The existing stale sentence appears only when the cloud copy could not be confirmed as current. The dialog has no images notice or sentence announcing the follow-up list.
Sharing needs you to be signed in and the app running. Signed out, pressing Share asks you to sign in first. Changes made while offline upload the next time you launch the app.
Supported files
| File | Published copy |
|---|---|
| Markdown | Original Markdown bytes |
.html, .htm | HTML page in a sandboxed frame, with inline CSS and JavaScript |
.json | One highlighted JSON code block |
.yaml, .yml | One highlighted YAML code block |
HTML can include local images supported by the image publisher. One scanner finds img elements
once per push for upload and address rewriting. It reads the first src of images in the
scripting-enabled DOM, excluding inert template content, and trims ASCII whitespace.
Remote and protocol-relative addresses stay unchanged.
Only the cloud copy changes. Supported inlined PNG, JPEG, GIF and WebP images are published as
separate images, including HTML srcset and CSS url() images; their payloads do not count toward
the 800 KiB cloud note limit. An inlined image that cannot be published stays inline and still counts.
A skipped neighbouring image still receives its public URL and remains broken. Neighbouring stylesheets, scripts,
fonts and pages are not published. These files still open read-only.
Image cleanup keeps an image rather than deleting one that may still be used. It compares raw and
percent-decoded names with raw, percent-decoded and HTML-entity-decoded content, including saved versions.
Valid %XX pairs work in either hex case; malformed escapes stay literal.
HTML pages wait their turn to be processed, with at most two pages processed at once.
If parsing fails or takes more than two seconds after it starts, that change publishes neither
images nor content, and the named file is marked out of date.
The 800 KiB limit applies to the final cloud copy, after publishing images and adding code fences.
A file whose text alone is over the limit is refused right away. A very large or very complex file
that cannot be processed in time is refused with a message naming it. Empty files cannot be shared.
Choose a space
If you belong to an organization, Share to offers Personal by default and your organization spaces. Members can publish their own copy to the organization. Every member of the organization can open copies in the sharing folder and all its subfolders. Only you and organization admins can change or remove your copy or its link. The local path is visible only to you. Anyone who has an active public link can read it.
One local file can have a public link in only one space at a time. If the file is already shared in another space, sharing it again refuses before creating a note or link, and the message names that space. To share it elsewhere, sharing has to be turned off there, or its cloud note removed there. Turning off only the link is enough; the note can stay. If that copy is in an organization folder you can only read, someone who can edit that folder has to remove it. The same rule stops you from turning on the link of an old copy while another space shares the file. When you leave an organization, your copies there no longer hold the file, so you can share it elsewhere, also when a link on such a copy stays on. If you join again while a copy in its sharing folder is still shared, the app pauses updates until you manage the copies in the cloud vault. The sidebar marks a present file as needing attention. One Review notice lists all your copies at that path, including copies published from another computer. If the file is missing, it lists only copies this computer published. An admin who works on your copy is told only that another space holds it, not which one. Copies created before this rule remain intact; if several match, manage them in their cloud spaces. Files at different paths on different computers remain separate.
If you rename or move a shared file to a path that another space already shares, its cloud copy does not follow. You see one message that says why; the app tries again after the file moves again or after you come back to the app window. The same happens when the app finds, at start, that a shared file was moved while it was closed. In that startup case, the file stays unbound and does not appear in the missing-file Review list. After a successful re-point, a later refusal at the same path can show a message again.
When an admin removes you from the organization, every public link on your copies in its sharing folder stops working, including links another admin published. Links you own on other copies in that folder stop too. Account deletion or purge revokes links you own in every organization's sharing folder. If you still belong to an organization, it also revokes every link on your copies there. The copies stay in the organization. Cancelling deletion does not restore links; share again. An admin can deliberately publish a retained copy after you leave. That new admin-owned link survives your later account deletion. Removing that admin or deleting their account revokes it.
The picker is locked while sharing is on. Turn sharing off before choosing a different space. If destination details cannot load, it keeps the bound destination and shows Cloud space until it can identify the personal space or organization. Publishing to an organization counts toward its note limit. If it is full, the message explains whether you can upgrade or who to contact.
In Personal, sharing reuses the root-level Shared local files folder and keeps its notes and subfolders. After preparation, a rename keeps that folder as the sharing root. In an organization, the app prepares its own sharing folder. If an ordinary root folder already has that name, sharing asks an admin to rename it before you try again. It does not change that folder's access. Only organization admins can rename, delete or manage access to the sharing folder. It stays at the root. Everyone keeps View access to it and to all its subfolders; admins cannot remove or reduce it, and no subfolder can be set to Hidden. Member access labels show View; you can still update your own copies.
Choose a folder
Use Folder to choose the sharing root or a readable subfolder. Each option shows the folder name first and its path after it, such as Project — Shared local files / Clients. Opening the dialog creates no folder. If a space has no sharing folder yet, Folder shows Shared local files (created on first share); the first share, or +, creates it. If your Personal space already has a top-level folder named Shared local files, Folder shows (will become the sharing folder): the first share uses that folder, with its notes and subfolders. In an organization, such a folder blocks sharing until an admin renames it, and the dialog says so. Every member of the organization can open copies in Shared local files and all its subfolders. You can change Folder while sharing is on. The copy moves and keeps its public link and versions. The space stays locked until you turn sharing off.
In Personal, or as an organization admin, use + to add a folder inside the selected folder. Type its name and press Create or Enter. Cancel or Escape closes the name field. Members choose existing folders; only organization admins can add them here.
This computer remembers, for your account, the space you last shared into and the last folder you shared into in each space. First use selects Personal and its root. If a remembered space or folder is no longer available, the dialog falls back to Personal or the sharing root. If subfolders fail to load, the dialog shows an error and keeps the root available. Use Retry folders to load them again.
Images
Images in the note travel with the share, including images inlined in the file itself. An image that is corrupt, too large, of an unsupported type or refused by the cloud stays as it is, and a message names it; the rest of the file still publishes. An inlined SVG in an HTML file stays inline without a message, because it shows anyway. Whatever stays inline still counts toward the 800 KiB limit; if it does not fit, the file is not shared and the message says why.
A message about the same file is shown once, not on every save. If the cloud could not be reached, Context Raven tries again on the next start or when you click Share.
A note holds at most 50 images. If you replace images in a file that already uses all 50, older versions in the note's history may show the new images. Swapping an image stored next to the file for an inlined one at exactly 50 images is refused with a message.
Stop sharing
Pressing Stop sharing in the local file's Share dialog stops this computer's link and deletes the cloud copy permanently. There is no delete checkbox in this dialog. The file on this computer stays. If the link cannot be revoked or the cloud copy cannot be deleted, Context Raven reports the failure.
Afterwards Context Raven looks in Shared local files in your personal and organization spaces for other live links it has no record of publishing from this computer. It lists only links recorded for a file with the same name, ignoring case and Unicode spelling differences, with the recorded path on each row. With no match, there is no offer. A renamed copy's link stays live; you can stop it in the cloud's Shared local files folder. Nothing is ticked in advance and nothing is stopped until you tick it and confirm — including the box that also removes those links' notes from your cloud space, which starts unticked here because the app cannot tell you what those notes are. A link somebody else has already stopped is reported as such and left alone.
If another share question covers this offer, a stop failure stays with its original question. If that question is replaced in the same signed-in session, an unread failure appears as a persistent error message that you can dismiss. A failure already displayed in the dialog is not repeated. These persistent messages survive navigation between files and pages. Signing out drops these outcomes and removes the messages, including after you leave the page. Known limit: if you leave the page while a stop is running, its eventual result has no dialog or fallback message.
When a shared file moves
When the app sees a shared file renamed or moved while running, it updates the cloud copy's stored path and title together. The title becomes the full filename, including its extension. This replaces a title edited by hand in the cloud. The public link, content and cloud folder stay the same. An offline, refused or conflicting update leaves both the cloud title and path unchanged. If a new filename exceeds the cloud title limit, the app explains that the filename is too long. It leaves the existing cloud copy in place and stops retrying that path on every rescan.
At launch, automatic recovery looks for exactly one file with a matching filename and identical
published content. A successful recovery uses the new path's full filename as the cloud title.
The filename comparison treats both / and \ as separators for Windows-recorded paths. This
also splits a literal \ in a macOS filename, so those names can match more loosely.
A rename made while the app was closed normally cannot be recovered by this search. When recovery
cannot identify the file, a persistent notice offers Stop sharing for its cloud copy.
Sharing and your other computers
A share belongs to the computer it was published from. That computer is the one that keeps the page up to date, notices if the file goes missing, and can stop the share. Another computer signed into the same account says nothing about the file — the share is healthy, it is simply not that computer's to manage, and a computer that never had the file cannot tell a deleted one from one that was never there.
It does speak about your cloud space, because it can read that. On that other computer the file shows as not shared, so sharing it there publishes a second page with its own link rather than taking over the first. Before publishing, Context Raven asks only about live links in your Shared local files folders that this computer does not track and whose recorded file name matches the local file's name. The comparison ignores letter case and treats NFC and NFD Unicode spellings as the same name, including paths recorded on Windows. The dialog lists only those matches. With no match, sharing proceeds without a question. After you confirm Create a second link, the question closes while publishing continues.
After Stop sharing, the offer lists only live links this computer does not track whose recorded file name matches the stopped file's name. You can stop those links without leaving the app.
Limits
- A matching name does not prove two links point at the same file. If a file was renamed after sharing from another computer or before the ownership record existed, sharing it can create a second link without a question. The old link stays live in Shared local files.
- A link on that list may be one this computer published before the app started keeping that record, or before it was reinstalled. It is still yours to stop; the app simply cannot account for it.
- If the cloud cannot be reached, sharing refuses rather than publishing a link it could not check against that folder first.
- If loading or refreshing finds several live copies at the same local path, Context Raven pauses updates for that file and leaves every copy and link unchanged. The sidebar and editor mark a present file as needing attention. One Review notice lists all your copies at that path, including copies published from another computer. If the file is missing, it lists only copies this computer published. The Share dialog also explains the conflict. A request already sent can still finish; the app starts no further write or automatic rebind after it detects the conflict. Open Shared local files in the intended cloud space to manage its copy. Review points you to the intended cloud space. Unresolved rows cannot stop or delete a copy from that panel. The app does not guess which copy moved. After you resolve the duplicates in the cloud, a complete refresh removes the obsolete recovery entries. A stop made before loading also refuses when several spaces make the intended copy unclear.
Overené / neoverené
| Check | Result |
|---|---|
| Organization access, departure revocation, restore conflicts | Verified through HTTP against a real test database |
| Flagged Personal roots, readable subfolders and destination defaults | Verified through HTTP, service and mounted component tests |
| Folder picker focus, Escape and responsive rendering | Previously verified in WebKit; updated button selectors unrun in the sandbox |
| HTML/JSON/YAML sharing (not released) | HTTP/Postgres and DOMParser checks cover image lifetime and quoting; browser/app pending |
| Same-name pre-share gate and after-stop offer | Service and mounted component tests; layout not measured in this change |
| Share / Stop sharing button geometry and theme colours | WebKit browser test, 375/768/1440, light and dark (first mate, 2026-10-30) |
| Installed desktop operation | Pending |