| 21 | | We have an increasing demand for more instances of Sahana eden to be set up and to show case certain aspects of the software. These demo sites are basically out-of-the-box Sahana Eden with certain modules enabled and a specific main menu hierarchy, along with a fixed set of data to populate the demo so that all of the required features can be easily showcased. |
| 22 | | |
| 23 | | Currently, their is a directory hierarchy private/prepopulate/demo which contains all of the perpopulate data and simple instructions on how to populate the database. What we want to add to this is a demo specific 000_config file. This file will hold the details of the modules that should be enabled, which includes their order on the main menu, It will also hold the prepopulate setting and any other settings specific to the demo. |
| 24 | | |
| 25 | | In 000_1st_run.py the template in the demo folder should be opened and the data copied into the 000_config.py file. After the file has been updated only those modules in the demo list shoudl be enables, all others should be disabled. Additionally, the prepopulate setting should be the same, along with teh registration settings. At the moment no other settings would need to be changed so each of these can be reeferenced directly in the code in 000_1st_run.py. |
| 26 | | |
| 27 | | One problem is that this code needs to know which prepopulate demo directory to look into to find the demo deployment settings, and these details are in the file we're looking for. So a new module will need to b created 00_demo_deploy.py which will be excluded from bzr and will set up the path to the demo deployment template. To help deployers, and an exampl eof waht this file should look like in 000_config.py. |
| | 21 | We have an increasing demand for instances of Sahana Eden to be set up quickly to show case certain aspects of the software. These demo sites are basically out-of-the-box Sahana Eden with a set of deployment_settings (e.g. certain modules enabled and a specific main menu hierarchy), along with a fixed set of data to populate the demo so that all of the required features can be easily showcased. |
| | 22 | |
| | 23 | Currently, there is a directory hierarchy {{{private/prepopulate/demo}}} which contains all of the prepopulate data and simple instructions on how to populate the database. What we want to add to this is a demo-specific {{{000_config.py}}} file. This file will hold just the deployment_settings which are different to the one in templates (e.g. details of the modules that should be enabled, which includes their order on the main menu, and the prepopulate setting). |
| | 24 | |
| | 25 | In {{{000_1st_run.py}}} the template in the demo folder should be opened and the data merged into the {{{000_config.py}}} file from {{{deployment-templates}}}. |
| | 26 | |
| | 27 | One issue is that this code needs to know which prepopulate demo directory to look into to find the demo deployment settings, and these details are in the file we're looking for. So a new file will need to be created: {{{models/0000_deploy.py}}}, which will be excluded from bzr, and will set up the path to the demo deployment template. To help deployers, an example of what this file should look like should be added to {{{000_config.py}}}. This could be as simple as just {{{demo = "Requests"}}} |
