Difference between revisions of "Amahi Sync"
| (6 intermediate revisions by one other user not shown) | |||
| Line 8: | Line 8: | ||
* Public files can be accessed via URLs under amahi.me. For instance, for an HDA called 'cpg', here is a sample url <code>http://cpg.amahi.me/Public/Amahi-logo.png</code> | * Public files can be accessed via URLs under amahi.me. For instance, for an HDA called 'cpg', here is a sample url <code>http://cpg.amahi.me/Public/Amahi-logo.png</code> | ||
| − | * All files (including public files) can be accessed via your Amahi.org control panel | + | * All files (including public files) can be accessed via a very easy to use your Amahi.org control panel, where you can copy the URL of public files to your clipboard with one click: |
| + | [[File:Amahi-sync-sshot.png]] | ||
| − | + | == Your own Files, Your own Subdomain == | |
| − | + | Each Amahi Sync account gets a free subdomain matching the nickname of your HDA under <code>amahi.me</code>. | |
| − | + | When you add shares to Amahi Sync, you can elect to share some of these files publicly from a subdomain of it's own. | |
| + | |||
| + | == Private and Public Sharing == | ||
| − | |||
By default, all the files in Amahi Sync's cloud are private. | By default, all the files in Amahi Sync's cloud are private. | ||
| Line 23: | Line 25: | ||
= Encryption and Security = | = Encryption and Security = | ||
| − | Encryption and Security is important for Amahi Sync. Transmission of the files is done via an encryption channel between your HDA and Amahi Sync's back-end servers. | + | Encryption and Security is important for Amahi Sync. |
| + | |||
| + | Amahi Sync's storage back-end is implemented with [http://aws.amazon.com/ Amazon Web Service's S3 service]. | ||
| + | |||
| + | Transmission of the files is done via an encryption channel between your HDA and Amahi Sync's back-end servers. | ||
The files are not kept encrypted, since they are accessed through the user control panel. As well, shares enabled as public, are accessed directly via the shared URLs. | The files are not kept encrypted, since they are accessed through the user control panel. As well, shares enabled as public, are accessed directly via the shared URLs. | ||
| + | |||
| + | |||
| + | [[Category:Apps]] | ||
Latest revision as of 23:42, 5 April 2014
Amahi Sync is an Amahi app for syncing, sharing and backing up files from HDA shares to the cloud.
Contents
How it works
Amahi Sync runs on your HDA and monitors files in certain shares that you enable for syncing. When new files are added or deleted to these shares or files change, they are automatically synced with Amahi's cloud storage.
Amahi Sync files can be accessed in two ways:
- Public files can be accessed via URLs under amahi.me. For instance, for an HDA called 'cpg', here is a sample url
http://cpg.amahi.me/Public/Amahi-logo.png - All files (including public files) can be accessed via a very easy to use your Amahi.org control panel, where you can copy the URL of public files to your clipboard with one click:
Your own Files, Your own Subdomain
Each Amahi Sync account gets a free subdomain matching the nickname of your HDA under amahi.me.
When you add shares to Amahi Sync, you can elect to share some of these files publicly from a subdomain of it's own.
Private and Public Sharing
By default, all the files in Amahi Sync's cloud are private.
However, you can set certain shares are "shared". This does not make the files publicly listed, however, you can share URL links to the files with anyone you want. If someone has the URL to the file, they can access the sync'ed copy of the file, until you delete the file from your share.
Encryption and Security
Encryption and Security is important for Amahi Sync.
Amahi Sync's storage back-end is implemented with Amazon Web Service's S3 service.
Transmission of the files is done via an encryption channel between your HDA and Amahi Sync's back-end servers.
The files are not kept encrypted, since they are accessed through the user control panel. As well, shares enabled as public, are accessed directly via the shared URLs.
