diff options
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 |