Problem
Jottacloud stores up to 5 previous versions of every file — a great feature. However, accessing these versions currently requires logging into the web interface with 2FA every time. For users relying on jotta-cli for headless/server backup workflows, this completely breaks the experience.
There is no CLI command to:
- List previous versions of a file
- Download a specific older version
Proposed Solution
Two new commands (or flags) would solve this:
jotta-cli versions <remote/path/to/file>
Lists all available revisions with: revision number, date, size, and checksum.
jotta-cli download --revision=N <remote/path/to/file> <local-destination>
Downloads a specific revision instead of only the current one.
Use Case
I run jotta-cli on a Windows server for automated backups. When I need to restore a previous version of a config file or database dump, I have to:
- Open browser
- Log in with 2FA
- Navigate to the file
- Click through the version history UI
- Download manually
This defeats the purpose of having a CLI tool for backup management. Being able to script version access would make Jottacloud significantly more useful for power users and server administrators.
Technical Context
The underlying infrastructure already supports this — the web application's FileService exposes a ListRevisions endpoint that returns revision metadata including download URLs. Exposing this existing capability through jotta-cli should be a relatively contained addition.
Alternative
If adding CLI commands is not planned, providing documented API access to file version history would allow the community to build tooling around it.
Problem
Jottacloud stores up to 5 previous versions of every file — a great feature. However, accessing these versions currently requires logging into the web interface with 2FA every time. For users relying on
jotta-clifor headless/server backup workflows, this completely breaks the experience.There is no CLI command to:
Proposed Solution
Two new commands (or flags) would solve this:
Lists all available revisions with: revision number, date, size, and checksum.
Downloads a specific revision instead of only the current one.
Use Case
I run
jotta-clion a Windows server for automated backups. When I need to restore a previous version of a config file or database dump, I have to:This defeats the purpose of having a CLI tool for backup management. Being able to script version access would make Jottacloud significantly more useful for power users and server administrators.
Technical Context
The underlying infrastructure already supports this — the web application's
FileServiceexposes aListRevisionsendpoint that returns revision metadata including download URLs. Exposing this existing capability throughjotta-clishould be a relatively contained addition.Alternative
If adding CLI commands is not planned, providing documented API access to file version history would allow the community to build tooling around it.