Repository navigation
Releases
Releases · theca-cloud/computer
1.2.0
Features
- drive: Libraries as drives on Linux, Windows and macOS
- logs: Logs to files, a day each, with their context
- libraries: A first step to choose them, and what new ones do
Fixes
- Core 1.6.2, a network error without its URL's query
- drive: A download never shows a drive's file under another name
The apps are not signed yet: how to open them.
1.1.0
Features
- Ignore files (.thecaignore): what they name is never uploaded
Fixes
- ci: Run the checks on prod and version tags, before any release
Documentation
- USING.md is theca.rs/computer: sprints keep it current
The apps are not signed yet: how to open them.
1.0.0
The first stable release: from now on, what the app keeps only moves forward, and its commands keep working within 1.x.
Breaking
theca add --auto-sync-mbis gone:theca account <account> --auto-sync-mb <n>sets it, and--folderan account's default folder.- The app's identifier is now
rs.theca.computer.
Features
- What the app keeps (its state file) is upgraded by every new version, 0.2.0's included: no more deleting it by hand. A copy of the previous one is kept beside it (
state.sqlite.v2), without the app password. - The app password moves into the system's keychain: the login keychain on macOS, the Credential Manager on Windows, the Secret Service on Linux. Where there is none (most headless servers), it stays in the state file and the login says so;
theca login --no-keyring(THECA_NO_KEYRING) keeps it there. Until the app is signed, each new version asks once on macOS to read it: click Always Allow. theca accountshows and changes an account's settings.- Exit codes: 3 when
theca statusfinds a folder not syncing, 4 when an account must log in again. Only 0 or not is promised; the codes are indications. - USING.md: installing it, the app password, headless use.
The apps are not signed yet: how to open them.
0.2.0
Breaking
- Needs a server on Theca's community edition 1.4.4 or later (
core1.4.0), and says so when logging in to an older one. - The state an earlier version wrote is refused: delete the file it names, then log in and add your folders again (their files stay, and are adopted).
Fixes
- A file is deleted or overwritten only if it is still the synced one, found by its file ID: on Linux, an unsynced
REPORT.txtbeside the syncedReport.txtcould be deleted. - A download never overwrites a file saved while it lands.
- Names are compared exactly as the server does; two server names that are one file on macOS or Windows (
σandς) are listed, never merged. - A first sync into a folder keeps the server's spelling of names (the next round renamed them on the server).
- An external disk mounted again is followed when its files show it's the same disk, and a folder stopped while its disk was gone syncs again by itself once it's back.
- Ctrl-C, SIGTERM and Quit stop within seconds, leaving no partial download behind.
- A folder that stops syncing is notified by the app, logged, and makes
theca statusfail. - A server restored from a backup is noticed even after new changes.
- Two state files never share a lock file.
The apps are not signed yet: how to open them.
A pre-release: keep a backup of the folders you sync. An upgrade may refuse the state an earlier version wrote (it is rewritten until 1.0): delete the file it names, then log in and add your folders again (their files stay, and are adopted).
0.1.0
Features
- The sync client: local folders kept identical to Theca libraries, both ways
- release: Packages for macOS, Windows and Linux, built and released on GitHub
Fixes
- gui: A long folder path no longer widens the window
- ci: The linux workflow runs only on a linux/amd64 agent
- tests: A stopped device's engine has stopped; failed scenarios show the engines' logs
- sync: A new file given a deleted file's inode is no move
- tests: Each scenario's database is dropped when it ends
- tests: The engine's notices and entries are awaited, not read at once after converging
- The sync client never loses a user's files (sprint 11)
Documentation
- ci: Our agents take only the workflows labelled for them
- ci: The Windows VM is started by hand, like the Mac agents
- ci: Starting and stopping the Mac and Windows agents, at the top
- readme: A Discord link, for questions, support and saying you run Theca
Build and CI
- release: Releases before 1.0 are GitHub pre-releases, saying to keep a backup
The apps are not signed yet: how to open them.
A pre-release: keep a backup of the folders you sync. An upgrade may need theca reset (the state is rewritten until 1.0).