Sha256: 2856d09faaaccdb576e33d1657d51200318d0db397f9398ef2edf909ffe6c85a
Contents?: true
Size: 1.79 KB
Versions: 11
Compression:
Stored size: 1.79 KB
Contents
Version 0.1 plan
================
INSTALLER
* Fix up apt so that we can handle it if it asks questions, or fail? Check with Ben
* Support alternate gem package sources - DONE
* MD5/SHA1 checking on the installation files?
MISC
* Growl support
* Do a merb example
* Fix up printing of output so that its nice and a bit more like ports - DONE
* print ports style output for stages (installing, configuring, etc...)
* Add an option to print the hierarchy tree of packages to be installed only - DONE
* BlankSlate - active support has one
* CREDITS file - DONE
* Get #!/usr/bin/env sprinkle working - DONE
OPERATING SYSTEM
* OS abstraction
* build essential on Ubuntu only for example
TESTING
* Test on a base system Ubuntu system - DONE
* Multiple runs, check system that's partially installed - DONE
* Resuming downloads with wget ok - DONE
ERRORS
* Need to think about handling errors nicely
* Recovering from an error, and or successive runs of sprinkle
* store installed state on the remote server so we can skip installed packages?
* what about self healing things later? need to think about it
DOCUMENTATION
* Document the code somewhat, at least review that its all ok
* Wiki
* Home page somewhere? point to github
* Blog post
* Screencast - use that cool screenflow tool?
Post Version 0.1 plan
=====================
CONFIGURATION
* Think about it - talk to Lincoln and Ben
* Use cap 2.3 send/download file helpers, might be useful somehow for transporting config files
ACTOR
* Investigate a pure net:ssh/gateway delivery mechanism, ie. without cap?
* Generate a cap task file as output? not sure if people would be interested in this?
* use ruby2ruby to generate the file, nice :)
MISC
* Slicehost API support for creating a slice on the way
* active resource
* SSH keys, have to deploy them somehow?
Version data entries
11 entries across 11 versions & 1 rubygems