diff options
Diffstat (limited to 'doc/ideas.rst')
-rw-r--r-- | doc/ideas.rst | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/doc/ideas.rst b/doc/ideas.rst index 86886f7..d84e8e8 100644 --- a/doc/ideas.rst +++ b/doc/ideas.rst @@ -9,14 +9,13 @@ Properties Connections ----------- -- :DEBIAN-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*. +- :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 |