|DarkFeather 49f9f6d315||8 months ago|
|examples||2 years ago|
|tests||8 months ago|
|.gitignore||8 months ago|
|LICENSE||8 months ago|
|Makefile||8 months ago|
|PKGBUILD||8 months ago|
|README.md||8 months ago|
|aether-gen.bash||2 years ago|
|aether.bash||4 years ago|
|make-user.bash||4 years ago|
|remote-backup||3 years ago|
The Aether project is a way to back up server configuration, source code, and file lists to remote locations. These remote locations should be securely controlled by the same administrative staff as the server owner.
The Aether project is the AniNIX’s implementation of the “cloud.” While its admins consider the computing cloud to be Computers Living On Unknown Datacenters, aka. with unknown controls and thereby insecure, distributing backups to many locations makes the AniNIX more resilient.
Dictionary.com translates Aether as the Greek personification of the clear sky, and this project lives a wide array of locations across the nebulous Internet, giving it no physical form to hold onto.
You have two options to install this project:
To create the aether and aether.pub files, run “make keys”. This should not be repeated.
Individual projects wanting to be backed up by the Aether system should add a file to their package into
Aether installs a script for rsync-based remote backups. We implement this policy through the two 4TB hard-drives, at least one of which is always off-site, that can be plugged into the Maat hotswap bay along with a virtual machine that mounts the ArchLinux iso and the drive in the bay.
The only client is direct server access on one of the client nodes.
Equivalent services are DropBox, Google Drive, or Barracuda.
Those deploying Aether should maintain a nodeslist file that only root can read.