Moving install to root for privileged scripts rather than the user; hooks cleanup; changing test strategey to helptext for now
This commit is contained in:
@@ -7,7 +7,7 @@ Dictionary.com translates Aether as the Greek personification of the clear sky,
|
||||
|
||||
# Installing
|
||||
You have two options to install this project:
|
||||
* Arch Linux and related distros: Run `makepkg -sri`
|
||||
* Arch Linux and related distributions: Install with `makepkg` or from AniNIX/Maat
|
||||
* Other operating systems: Run `make install`
|
||||
|
||||
## Initial setup
|
||||
@@ -20,11 +20,17 @@ Individual projects wanting to be backed up by the Aether system should add a fi
|
||||
A SIEM filter should be set up to search for successful logins of the `aether` user.
|
||||
|
||||
# Relevant Files and Software
|
||||
Aether installs a script for rsync-based remote backups. We implement this policy through the two 8TB hard-drives, at least one of which is always off-site, that can be plugged into a hotswap bay of a hypervisor along with a virtual machine that mounts the ArchLinux iso and the drive. Admins use the included ssh daemon in the iso to present the drive as a backup target,
|
||||
Aether installs a script for rsync-based remote backups. We implement this policy through the two 8TB hard-drives, at least one of which is always off-site, that can be plugged into a hot-swap bay of a hypervisor along with a virtual machine that mounts the ArchLinux iso and the drive. Admins use the included ssh daemon in the iso to present the drive as a backup target, or the backup drive can be mounted directly onto Core via a SATA cage
|
||||
|
||||
An additional backup is the generated `/home/aether/aether.enc` file. This is a more targeted backup of databases and file indexes.
|
||||
|
||||
Keep in mind that all of [AniNIX/Foundation](https://foundation.aninix.net) is naturally a backup solution -- so long as anyone has a clone of the repo, the data survives.
|
||||
Keep in mind that all of [AniNIX/Foundation](https://foundation.aninix.net) is naturally a backup solution -- so long as anyone has a clone of the repo, the data survives. Aether should only be used to back up databases, such as the following:
|
||||
|
||||
* Anope DB
|
||||
* PostgreSQL
|
||||
* Elasticsearch
|
||||
|
||||
One should have significant care before using the aether.enc solution for tools like AniNIX/Yggdrasil or AniNIX/Foundation.
|
||||
|
||||
# Available Clients
|
||||
The only client is direct server access on one of the client nodes.
|
||||
@@ -33,4 +39,4 @@ The only client is direct server access on one of the client nodes.
|
||||
Equivalent services are DropBox, Google Drive, iCloud, or OneDrive.
|
||||
|
||||
# Notes
|
||||
Those deploying Aether should maintain a nodeslist file that only root can read.
|
||||
Those deploying Aether should track the `/home/aether/.ssh/authorized_keys` file strongly on the generating server, so that all keys are specifically tracked for their origin & who handles them.
|
||||
|
||||
Reference in New Issue
Block a user