summaryrefslogtreecommitdiff
path: root/debian/control
blob: 7c17d0e12ae2f90762270baf57aa0b5028e81184 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Source: byteback
Section: ruby
Priority: optional
Maintainer: Patrick J Cherry <patrick@bytemark.co.uk>
Uploaders: Steve Kemp <steve@bytemark.co.uk>
Build-Depends: debhelper (>= 7.0.50~), txt2man
Standards-Version: 3.9.6
# Vcs-Git:
Vcs-Browser: https://projects.bytemark.co.uk/projects/byteback/repository
Homepage: https://projects.bytemark.co.uk/projects/byteback

Package: byteback
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ruby | ruby-interpreter, rsync, openssh-client, ruby-ffi | libffi-ruby
Description: Maintenance-free client & server backup scripts for Linux
 byteback encapsulates Bytemark's "best practice" for maintenance-free backups
 with easy client and server setup.
 .
 "Maintenance-free" means that we'd rather make full use of a fixed amount of
 disc space.  Management of disc space must be completely automatic, so the
 process never grinds to a halt for reasons that could be automatically
 resolved.  Failed backups can be restarted in case of network problems.
 .
 We use the standard OpenSSH on the server for encrypted transport & access
 control, btrfs for simple snapshots and rsync for efficient data transfer
 across the network.
 .
 Backups should require as little configuration as possible to be safe - just
 the server address should be enough.