aboutsummaryrefslogtreecommitdiff
path: root/debian/control
blob: a1a6af3ae24a7f65cdc085106860a804942fdd17 (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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
Source: consfigurator
Section: admin
Priority: optional
Maintainer: Sean Whitton <spwhitton@spwhitton.name>
Build-Depends:
 cl-agnostic-lizard,
 cl-alexandria,
 cl-anaphora,
 cl-babel,
 cl-bordeaux-threads,
 cl-cffi,
 cl-closer-mop,
 cl-heredoc,
 cl-interpol,
 cl-named-readtables,
 cl-osicat,
 cl-ppcre,
 cl-trivial-backtrace,
 debhelper-compat (= 13),
 dh-elpa,
 libacl1-dev,
 libcap-dev,
 python3-sphinx,
 python3-sphinx-rtd-theme,
 sbcl,
 sphinx-common,
 texinfo,
Standards-Version: 4.5.1
Homepage: https://spwhitton.name/tech/code/consfigurator/
Vcs-Git: https://git.spwhitton.name/consfigurator/
Vcs-Browser: https://git.spwhitton.name/consfigurator/
Rules-Requires-Root: no

Package: cl-consfigurator
Architecture: all
Depends:
 cl-agnostic-lizard,
 cl-alexandria,
 cl-anaphora,
 cl-babel,
 cl-bordeaux-threads,
 cl-cffi,
 cl-closer-mop,
 cl-heredoc,
 cl-interpol,
 cl-named-readtables,
 cl-osicat,
 cl-ppcre,
 cl-trivial-backtrace,
 emacsen-common,
 libacl1-dev,
 libcap-dev,
 ${misc:Depends},
Recommends:
 emacs,
 sbcl,
 ${sphinxdoc:Depends},
Provides:
 consfigurator,
 elpa-consfigurator,
Built-Using:
 ${sphinxdoc:Built-Using},
Description: Lisp declarative configuration management system
 Consfigurator is a system for declarative configuration management using
 Common Lisp.  You can use it to configure hosts as root, deploy services as
 unprivileged users, build and deploy containers, install operating systems,
 produce disc images, and more.  Some key advantages:
 .
  * Apply configuration by transparently starting up another Lisp image on the
    machine to be configured, so that you can use the full power of Common Lisp
    to inspect and control the host.
 .
  * Also define properties of hosts in a more restricted language, that of
    :POSIX properties, to configure machines, containers and user accounts
    where you can't install Lisp.  These properties can be applied using just
    an SSH or serial connection, but they can also be applied by remote Lisp
    images, enabling code reuse.
 .
  * Flexibly chain and nest methods of connecting to hosts.  For example, you
    could have Consfigurator SSH to a host, sudo to root, start up Lisp, use
    the setns(2) system call to enter a Linux container, and then deploy a
    service.  Secrets, and other prerequisite data, are properly passed along.
 .
  * Combine declarative semantics for defining hosts and services with a
    multiparadigmatic general-purpose programming language that won't get in
    your way.
 .
 Declarative configuration management systems like Consfigurator and Propellor
 share a number of goals with projects like the GNU Guix System and NixOS.
 However, tools like Consfigurator and Propellor try to layer the power of
 declarative and reproducible configuration semantics on top of traditional,
 battle-tested UNIX system administration infrastructure like distro package
 managers, package archives and daemon configuration mechanisms, rather than
 seeking to replace any of those.  Let's get as much as we can out of all that
 existing distro policy-compliant work!