just for reference - here's an earlier (4.6->4.7->5.0) incarnation of CVS deployment
dman - June 13, 2007 - 02:45
| Project: | CVS deploy |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Needs work, but does the trick for my dev sites.
http://coders.co.nz/drupal_development/?q=node/550
Mentioned previously here
# It scans cvs.drupal.org for all modules (in realtime)
# It can CVS checkout any listed module, as 'anonymous', optionally with a version tag
Um, doesn't this cross over a lot with Module Installer Project ?
(This is not an issue, just an FYI. Close it as you see fit.)
#1
re: http://drupal.org/project/module_installer
after a quick scan of the source, that's another failed attempt at automatic upgrades that doesn't concern itself with security. :( that's having the drupal admin interface update itself. the script i'm talking about will be a CLI script to run completely outside of the web interface. the website remains totally read-only to the uid that httpd is running as. the CLI script is run manually, by an admin human with priviledged shell access (which we can assume by definition for sites deployed by CVS).
thanks for the pointer to your older effort, too. however, the difference is that the thing i'm talking about will be integrated with update_status.module, so that you get the latest recommended release (or, hopefully, integrated with the update_status UI, so you can select which of the available updates you'd like to upgrade to (the latest from the same branch, the latest from a newer branch, etc)). therefore, instead of scanning all of the contrib CVS repo, it just looks at the data update_status already knows about what you've got installed and what's available, and this script just generates the cvs update commands necessary to update your site.
thanks for your interest,
-derek