On this page
Remote module installer
proposed by: bevan
This idea comes from a bit of experience with Joomla, recent usage (and appreciation) of release monitor module, and a bit of a imagination.
Currently to install a module on a remote drupal installation, a drupal devel (typically) visits drupal.org/project/MODNAME (or navigates to it), downloads it to their loacl machine, uploads it to their drupal server, unpacks it (sometimes ina different order), logs in to the drupal site, enables the module, then gets on with their task and job.
This process is the same almost every time, and can be done up to several times a day. Although admittedly it doesn't take long, the time it takes is significant when it is done many times, and is a rather mundane task that has no variation each time it's done. So what's technology's answer for these repetitive boring mundane human-error prone tasks? AUTOMATION!
You probably guessed it already, the objective of this proposal is to create a system by which devels can install modules available on drupal.org in about 3 clicks:
- choose module
- choose version
- download/install/enable
Obviously there would be some security issues to be aware of and handle appropriately here. Integration with drupal.org and probably CVS would be required, and this may lead to the recommendation of changes to drupal.org, CVS, or module maintainer's systems / habits.
For better usability, "1. choose module" may be more than one click. modules could be categorized for selection in the same way they are on drupal.org. the module could even proxy drupal.org to provide selection, drupal.org user profile's could include an option and field to allow devels to install modules right from drupal.org/project/MODNAME (more difficult security measures to worry about with that one! ;) ).
Release Monitor already covers a small portion of the code that would be required for this project. This project could be an extension of Release Monitor, dependent on it, or independent.
Comments on this proposal
live-search text input field
Bevan - February 17, 2007 - 04:38
"1. choose module" could alternatively provide a live-search text input field. Wouldn't that be fun :)
======================================================
======================================================
I just found Module
Bevan - February 18, 2007 - 04:39
I just found Module Installer module: http://drupal.org/node/119435
It does the other half. Now the project would just involve integrating the two, and doing all the necessary security checks on each and the integration, documentation, and proposing changes (if any to CVS and/or drupal.org).
I wonder if that makes it too small a SoC project?
======================================================
======================================================
there's also this:
Bevan - February 18, 2007 - 04:39
there's also this: http://drupal.org/node/119435
======================================================
======================================================
you could add the security update too
snufkin - February 19, 2007 - 21:07
I think the update system proposed in the blogger profile topic could fit this project well, making it a whole update/install mechanism.
======================================================
======================================================
I moved this to "needs work"
webchick - February 22, 2007 - 10:17
because:
a) the proposal needs to be re-scoped, factoring in module_installer + release_monitor
b) deliverables need to be clearer.
c) security issues need to be addressed.
something suggested by Heine was creating a way for Drupal to SFTP files to the server, rather than having to chmod 777 modules which presents a gaping insecure entry point for a malicious person.
======================================================
======================================================
Is this any good ?
seancharles - March 16, 2007 - 14:45
Just finished the first release, would appreciate feedback.
It can also be used to install themes as well; I just installed 15 Drupal 5 themes by changing the installation folder to .../themes instead of modules.... with a bit of work (when I have time) I am going to make it scan for themes and updates and make it easy peasy to install.
I have contemplated writing a Flash UI for this just to save on all the page to-in and fro-ing.
Comments ?
======================================================
======================================================
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion