diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2021-07-20 14:30:15 -0700 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2021-07-24 12:00:33 -0700 |
| commit | 5f69000e489b3840e07925a5b2f21ce3bc8adbd6 (patch) | |
| tree | efce18e0bf2821d96514e25ed4c28de91b1d8db1 /doc | |
| parent | fd39aa568bb823b82dbd33f9e8e00226b2c0ae1b (diff) | |
| download | consfigurator-5f69000e489b3840e07925a5b2f21ce3bc8adbd6.tar.gz | |
add IMAGE-DUMPED and CRON:RUNS-CONSFIGURATOR
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ideas.rst | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/ideas.rst b/doc/ideas.rst index 11f8c12..5ff4795 100644 --- a/doc/ideas.rst +++ b/doc/ideas.rst @@ -12,14 +12,6 @@ Properties Connections ----------- -- :SBCL could (fork and) SAVE-LISP-AND-DIE. That way, we have something that - a cronjob can call to re-run the deployment to ensure that all properties - remain applied. Need to think about how the property which sets up the - cronjob will be specified in consfigs -- does it make sense to allow passing - in arbitrary deployments, or do we only allow re-running exactly the same - thing? If the former, the saved image will need to take some sort of - command line input telling it what arguments to pass to DEPLOY*. - - Basic infrastructure for connections which work with just input and output streams connected to an interactive POSIX sh somewhere, like TRAMP, and probably using ``base64 -d`` for WRITEFILE. Probably the basic connection |