HI, Just wondering if there is a project going on with making an install file to drupal? So you just upload your drupal files to your webhotel and then go to your www.yourdomain.com and set up your drupal installation. After succesed installation the normal drupal interface will appear at www.yourdomain.com. Like when you install Gallery2... If it's not the case, I'll be willing to help out here, it would ease up the installation a bit. -- Best Regards René Madsen
there is something like this on the plate for a long, long time.. Adrian Rossouw worked on this till half a year a go, after that i thouth Neill Drumm proceeded his work. you should contact those guys, they are both on this list.. Steef Op 8-jan-2006, om 19:56 heeft Schultz Consult - [René Madsen] het volgende geschreven:
HI,
Just wondering if there is a project going on with making an install file to drupal?
So you just upload your drupal files to your webhotel and then go to your www.yourdomain.com and set up your drupal installation.
After succesed installation the normal drupal interface will appear at www.yourdomain.com.
Like when you install Gallery2...
If it's not the case, I'll be willing to help out here, it would ease up the installation a bit.
-- Best Regards René Madsen
--- Stefan Nagtegaal Drupal-Devel@iStyledThis.nl Drupal Development Mailinglist
Stefan wrote:
there is something like this on the plate for a long, long time.. Adrian Rossouw worked on this till half a year a go, after that i thouth Neill Drumm proceeded his work. you should contact those guys, they are both on this list..
I haven't actually done much with install itself since I chose to tackle upgrading first. Next up for me is module installation, which will eliminate .(my|pg)sql files. The lack of a module dependency system is more of a problem than not having an installer, chx has an excellent patch for that. Manual installation works and is well documented so it is not the biggest problem right now. For installation there are a couple efforts. This is all from memory so please correct and add to the list as needed. It would help a lot in my session planning for Vancouver. CivicSpace's installer, maintained by Ankur. This is very big and has a lot of CivicSpace hard coded in. A lot could be done to remove code duplication with core, but there may be functions which cannot currently be bootstrapped without a database. Bryght's provisioning system developed by Adrian is closed source. Last I knew CivicSpace was getting a license of some sort for one or two projects which are going to go live real soon now. Vlado is working on a command line installation framework which might be able to be used with other webapps, comparable to apt. I don't know much about that one. Two related things which are lower priority than an installer are post-installation configuration and site profiles. These two things would be nice to have, but there are existing tasks that aren't going away which can be made better first.
Op 8-jan-2006, om 19:56 heeft Schultz Consult - [René Madsen] het volgende geschreven:
If it's not the case, I'll be willing to help out here, it would ease up the installation a bit.
Whats your plan? -- Neil Drumm http://delocalizedham.com/
On 09 Jan 2006, at 3:11 AM, Neil Drumm wrote:
Stefan wrote:
there is something like this on the plate for a long, long time.. Adrian Rossouw worked on this till half a year a go, after that i thouth Neill Drumm proceeded his work. you should contact those guys, they are both on this list.. The forms api work was also part of the install system work, it was aimed at making workflows (wizards) easier to create.
As such, I believe we can finally get the install system (of which drumm already did the upgrade parts) into core for 4.8.
I haven't actually done much with install itself since I chose to tackle upgrading first. Next up for me is module installation, which will eliminate .(my|pg)sql files. The lack of a module dependency system is more of a problem than not having an installer, chx has an excellent patch for that. Manual installation works and is well documented so it is not the biggest problem right now.
For installation there are a couple efforts. This is all from memory so please correct and add to the list as needed. It would help a lot in my session planning for Vancouver. http://www.drupal.org/install-system-overview
Same project, different aspects.
CivicSpace's installer, maintained by Ankur. This is very big and has a lot of CivicSpace hard coded in. A lot could be done to remove code duplication with core, but there may be functions which cannot currently be bootstrapped without a database. I originally wrote the installer for civicspace, and the wizard api I designed, but decided not to implement for drupal 4.4 (back in the day) is being used for it, primarily because of all the code duplication.
Also, the forms API was written to make these wizards easier to write, so the install wizard script should be re-evaluated for 4.7.
Bryght's provisioning system developed by Adrian is closed source. Last I knew CivicSpace was getting a license of some sort for one or two projects which are going to go live real soon now.
All the drupal code is open source, and exists as patches on drupal.org. The only stuff that is not distributable is the python scripts in the backend, and our hosting system / client database schemas. This system is far from being a generic installer, and is used for maintaining large (thousands of sites) installations, cleanly and easily. This kind of thing is expressly based on removing any user interface and automating as much as possible. For this, .install files (as with your upgrade work) are used, and in fact, you originally got the code from me.
Vlado is working on a command line installation framework which might be able to be used with other webapps, comparable to apt. I don't know much about that one. Vlado wrote a generic package dependency system, and scripts which inferred a lot of this from module_invoke use. It still invokes .install files for each of the packages it installs, and as such is part of the same solution, not a solution of it's own.
It introduces stuff such as virtual packages, which allows us to very easily do install profiles and the like.
Two related things which are lower priority than an installer are post-installation configuration and site profiles. These two things would be nice to have, but there are existing tasks that aren't going away which can be made better first. These are two things which are 'free' if we use a proper package dependency sytem.
-- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
On 8-Jan-06, at 7:14 PM, Adrian Rossouw wrote:
Bryght's provisioning system developed by Adrian is closed source. Last I knew CivicSpace was getting a license of some sort for one or two projects which are going to go live real soon now. All the drupal code is open source, and exists as patches on drupal.org.
Yes, just wanted to clear up *any* misconceptions. All of the Drupal- related items are all open source, and are being given back to the community. Adrian's work on .install files will hopefully lead towards having a module install system which, as Neil says, does not include .mysql files and provides the basis for upgrading as well. That leaves us only a step or two away from install profiles. There are some .install files out in the wild (amazon associates, IIRC), used mainly for updates at this point, since Neil's updater got in to 4.7 but the other components of the installer did not. Adrian, perhaps you can point to the patches so that people know where to look.
The only stuff that is not distributable is the python scripts in the backend, and our hosting system / client database schemas. This system is far from being a generic installer, and is used for maintaining large (thousands of sites) installations, cleanly and easily.
Our provisioning system is closed source at this time...it is only of use if you are maintaining 100s or 1000s of accounts and is written in Python/Postgresql. If any hosting providers are interested in working with us...feel free to contact me directly. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 SKYPE borismann http://www.bryght.com
Op maandag 09 januari 2006 02:11, schreef Neil Drumm:
Bryght's provisioning system developed by Adrian is closed source. Last I knew CivicSpace was getting a license of some sort for one or two projects which are going to go live real soon now.
For sympal, our server maintainer is rewriting parts of an open source provisioning system. As soon as we have it all running and tested, as soon as the most annoying bugs and glitches are out, I will report back here. For now you can find it at diskhosting.sourceforge.net (or was it dischosting...?). It already has a mambo, and drupal installer built in. It is, by no means usable for joe Average, but once you have it installed on your hosting provider system, joe average can install Drupal from there very easy. Bèr
participants (6)
-
"Schultz Consult - [René Madsen]" -
Adrian Rossouw -
Boris Mann -
Bèr Kessels -
Neil Drumm -
Stefan