You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
storage: 'No universal hosted free quota; storage depends on your Seafile server or provider.',
591
-
limits: 'Quota, WebDAV, library encryption, and version retention are deployment-specific.',
592
-
billing: 'Community/self-hosted deployments use your infrastructure; hosted providers may charge separately.',
593
-
bestFor: 'Self-hosted file sync libraries and team shares.',
594
-
costTip: 'Check library history/version retention before large syncs; old versions can consume more storage than expected.',
595
-
sourceLabel: 'Seafile documentation',
596
-
sourceUrl: 'https://manual.seafile.com/',
589
+
badges: ['TRIAL','SELF-HOST','BYO'],
590
+
storage: 'Self-hosted Seafile uses your own storage. In an observed Seafile Plus hosted account, the Team Plan Trial exposed 1 GB total for up to 3 users.',
591
+
limits: 'Observed hosted trial included 300 GB monthly traffic and 6 monthly AI credits. Per-user quota inside the organization is admin-configurable and should not be treated as plan data.',
592
+
billing: 'Self-hosted deployments use your infrastructure. Observed Seafile Plus Team Plan Trial was USD 0, deactivated after 30 days, and could currently be reactivated from reminder email links within the retention window.',
593
+
bestFor: 'Self-hosted file libraries or testing the managed Seafile Plus cloud before deciding on a paid hosted plan.',
594
+
costTip: 'When documenting Seafile Plus, use the organization plan page for commercial limits and treat per-user quota settings as tenant-specific admin configuration.',
Copy file name to clipboardExpand all lines: features/aerocloud.md
+38-60Lines changed: 38 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,63 +4,41 @@ AeroCloud turns any server into a private personal cloud. It rides AeroFTP's ful
4
4
5
5
## Supported Integrations
6
6
7
-
AeroCloud supports the entire provider surface for sync (GitHub and Drime Cloud are excluded - conceptually incompatible with sync). Providers are classified by sync reliability:
Cloud services that authenticate via OAuth 2.0. AeroFTP handles the full authorization flow - click **Authorize**, sign in to the provider, and the token is stored securely in the vault.
30
-
31
-
| Provider | Free Tier | Auth | Special Features |
AeroCloud supports the sync surface exposed by the desktop wizard. The maturity badges below are the same ones used in the app. `GitHub` and `Drime Cloud` are excluded from AeroCloud sync because their models do not fit the background-sync workflow.
| FTP | Username / Password | Beta | Requires MFMT support for reliable timestamps. |
14
+
| FTPS | Username / Password | Beta | Requires MFMT support for reliable timestamps. |
15
+
| SFTP | Password / Key / Agent | Stable | Best overall fit for full AeroCloud sync. |
16
+
| WebDAV family | Username / Password | Stable | Covers generic WebDAV plus hosted variants such as Nextcloud, Seafile, Tab.digital, Felicloud, CloudMe, InfiniCLOUD, Jianguoyun, and similar presets. |
17
+
| S3 family | Access Key / Secret | Stable | Covers AWS S3, Cloudflare R2, Backblaze S3, Wasabi, DigitalOcean Spaces, MinIO, Oracle Cloud, S3Drive, and similar S3-compatible presets. |
18
+
| Azure Blob | Connection string / SAS | Stable | Treated as a first-class object-storage sync target in the wizard. |
19
+
| Google Drive | OAuth 2.0 PKCE | Stable | Native Google API path with strong sync behavior. |
20
+
| Dropbox | OAuth 2.0 PKCE | Stable | Native Dropbox API path with strong sync behavior. |
21
+
| OneDrive | OAuth 2.0 PKCE | Stable | Native Microsoft Graph path with strong sync behavior. |
22
+
| Jottacloud | Username / Password | Stable | Native provider with no wizard caveat. |
23
+
| kDrive | OAuth 2.0 | Stable | Native provider with no wizard caveat. |
24
+
| Koofr | OAuth 2.0 PKCE | Stable | Native provider with no wizard caveat. |
25
+
| OpenDrive | Session auth | Stable | Native provider with no wizard caveat. |
26
+
| Box | OAuth 2.0 | Beta | Stricter API rate limits than other providers. |
| FileLu | API key / saved profile | Beta | Region latency can vary; sync uses hash comparison. |
34
+
| 4shared | OAuth 1.0 | Alpha | Manual re-authorization is required if the token is revoked. |
35
+
36
+
### How To Read The Matrix
37
+
38
+
-**Stable** means the wizard treats the integration as production-grade for day-to-day AeroCloud usage.
39
+
-**Beta** means the integration is usable, but the desktop app exposes a concrete caveat in the wizard.
40
+
-**Alpha** means the integration is available, but operational rough edges are still expected.
41
+
-**WebDAV family** and **S3 family** are documented by analogy: if a preset is not shown as its own row in the AeroCloud wizard, it inherits the family tier unless its provider guide states otherwise.
64
42
65
43
## Background Sync
66
44
@@ -82,9 +60,9 @@ The CloudPanel wizard guides you through connecting a new cloud provider in four
82
60
83
61
A grid of protocol cards organized into three groups:
|**Nextcloud**|`/remote.php/dav/files/USERNAME/`| 443 | Varies by provider | Replace `USERNAME` with your exact login name |
33
-
|**Seafile**|`/seafdav`| 443 |2 GB | SeafDAV must be enabled by the server admin|
33
+
|**Seafile**|`/seafdav`| 443 |Varies by deployment | Self-hosted and hosted Seafile services use the same SeafDAV path|
34
34
|**CloudMe**|`/` (host: `webdav.cloudme.com`) | 443 | 3 GB | Direct WebDAV access, no path prefix needed |
35
35
|**Felicloud**|`/remote.php/dav/files/USERNAME/`| 443 | 10 GB | Hosted Nextcloud-based service with the same DAV path pattern |
36
36
|**Custom**| Any path | Any | -- | For any WebDAV-compatible server or NAS |
@@ -54,7 +54,7 @@ Seafile uses the SeafDAV extension for WebDAV access:
54
54
2. Enter your Seafile server hostname.
55
55
3. Use your Seafile account credentials.
56
56
57
-
> **Note**: SeafDAV must be enabled by the Seafile server administrator. Check `seahub_settings.py` for `ENABLE_WEBDAV_SECRET`. If it is not enabled, you will receive a 404 error on the WebDAV endpoint.
57
+
> **Note**: On self-hosted Seafile, SeafDAV must be enabled by the server administrator. Check `seahub_settings.py` for `ENABLE_WEBDAV_SECRET`. Hosted Seafile services typically manage this for you. If SeafDAV is disabled, you will receive a 404 error on the WebDAV endpoint.
0 commit comments