Changes between Version 30 and Version 31 of BluePrintWebSetup

Timestamp:

09/27/10 19:57:57 (15 years ago)

Author:

Fran Boon

Comment:

--

BluePrintWebSetup

@@ -9 +9 @@
 }}}
 
+=== !ToDo ===
+==== Packaging ====
 We need to think about how we package this since it's designed as a parallel app to eden, so would normally sit at the same level as the
 current repo's root folder. Don't really want to move the root up one as then we'll find it harder to maintain parallel app versions.
@@ -14 +16 @@
 Thinking about storing it within /eden but then having it copy this stuff out to the root applications folder on run, if it's not there
 already....thinking about how it updates that version & how we'd manage with eden, eden2, eden_test as alternate app versions...
+
+==== Maintainability ====
+I think we should look to redesign this somewhat:
+ 1. Pull all setting options from s3cfg.py & current settings from 000_config.py.
+Remember that the idea is that web setup can be run after the initial install to make subsequent settings changes (ideally just single
+pages, but skipping unchanged pages via Next is fine for now).
+The validation for fields needs to be pushed back into s3cfg so that these get maintained together & can be read by setup when it imports
+from there (other than what you're doing in the view for password & HMAC key - these can stay as-is).
+
+ 2. Don't do a full write-out of the 000_config file.
+Instead just touch what we know - i.e. parse the existing file & just change lines that we know.
+If a line doesn't exist (either commented or active) then can add it from the information in s3cfg.
+If a line does exist (either commented or active) then can uncomment & set to what has been requested.
+All other lines should be ignored.
+This would seem a more robust, less intrusive system.
+I can foresee that deployers will add their own customisations into 000_config & won't push this into s3cfg or setup & will get upset if their customisations disappear...
+
+==== i18n ====
+ * all user-visible strings should be wrapped in T()
 == Requirements ==
 Provide a 1st-time configuration screen.