| Version 35 (modified by , 14 years ago) ( diff ) |
|---|
Release Process
When making a Stable Branch from which to build releases, we need to do these tasks:
Check that all works with a released version of Web2Py
Ensure included files sane:
- README
- VERSION (updated automatically by Bzr start-commit hook)
- INSTALL
- CHANGELOG
Clear Database
To clear database of test data & reset to defaults:
- Close Web2Py
- Delete all files from
/databases
NB This assumes that all required settings are being generated upon intialisation as per the Framework
Export Application
- Clean: http://127.0.0.1:8000/admin/default/cleanup/eden
- Compile: http://127.0.0.1:8000/admin/default/compile_app/eden
- NB If this Errors then this is likely to be a faulty view (e.g. missing a final {{pass}}) which needs resolving before the release to avoid performance issues.
- Pack all: http://127.0.0.1:8000/admin/default/pack/eden
- Save as:
web2py.app.eden-0.x.w2p
This could be scripted:
cd /home/web2py # @ToDo: Clean # Compile python web2py.py -S eden -M -R applications/eden/static/scripts/tools/compile.py # @ToDo: Catch errors # @ToDo: Pack # @ToDo: Download with filename
Upload to LaunchPad
- Register a new release: https://launchpad.net/sahana-eden/trunk/+addrelease
- Add download file
Update Windows Installers
Update Wiki
Update Demo
- Update Web2Py (if necessary)
cd /home/web2py/applications/eden bzr pull -r xxx
Alternate approach:
- Start appadmin: /root/web2py_admin.sh
- Configure SSH Tunnel: http://web2py.com/AlterEgo/default/show/143
- Access via SSH Tunnel: http://127.0.0.1:8001/admin
- Upload application: http://127.0.0.1:8001/admin/default/site
- Reboot VPS (free up resources for improved performance)
Ideas
Note:
See TracWiki
for help on using the wiki.
