TODO NOW:
-- Consider adding user config to repository
-- Put php.ini links in repos (probably will need another
- script in .scripts)
-- Version configuration
-
-- Consider making usermode wizard operation a support mode
- (mostly for letting users upgrade things themself)
+- Better error message if daemon/scripts-security-upd
+ is not on scripts-security-upd list
- Add repository flag to migrate so that we can specify an
arbitrary repository to migrate to
+- Build automation for generating config files; this automation
+ will be shared with the migrate script and the installer script
+ (migrate script needs to be able to pull out values from config
+ file, so will we; installer script needs to be able to run
+ the installer to generate config files, so will this)
+
- The great initial deploy:
- Turn on mediawiki new autoinstaller
- - Migrate all mediawik installs
+ - Migrate all mediawiki installs
+
+- Consider making usermode wizard operation a support mode
+ (mostly for letting users upgrade things themself)
- Implement proper deploy log parsing; this basically means we
need to be able to introspect Git Log. Consider using git-python
its latest version (do this after its migration)
- Wordpress needs to check for php.ini files (which it almost
certianly has) and commit messages
+- Wordpress needs user config and php.ini links made
- Summary script should be more machine friendly, and should not
output summary charts when I increase specificity