FYI: Plesk 8.2 offers Drupal as a site application
Page 5 on http://www.swsoft.com/r/pdfs/Plesk/plesk82_whatsnew.pdf Joomla and Xoops are also listed as new additions. -K
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karthik schrieb:
Page 5 on http://www.swsoft.com/r/pdfs/Plesk/plesk82_whatsnew.pdf
Does nybody know how the internals of Plesk work? Specifically: Does it have a push mechanism for updates? Or is it as uch a problem as fantastico? Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGlxyOfg6TFvELooQRAjsyAKDDbKDNYCniwUkdciv5rsGggJfE4ACgnAjR 6gu6+YkoPms2Vtax20tNPOM= =Mdf/ -----END PGP SIGNATURE-----
Gerhard Killesreiter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karthik schrieb:
Page 5 on http://www.swsoft.com/r/pdfs/Plesk/plesk82_whatsnew.pdf
Does nybody know how the internals of Plesk work? Specifically: Does it have a push mechanism for updates? Or is it as uch a problem as fantastico?
Plesk runs an autoinstaller program that pings back to check for updates and notifies users with sufficient privileges upon login (namely admin). You can upgrade directly from the web administration panel but i normally find it best to run /usr/local/psa/admin/sbin/autoinstaller from CLI as root to monitor progress and catch errors as they happen. This update system really only affects Plesk packages and not OS packages. Frequent updates to the Application Library that contains the various installable Applications are available but i elect to just manually install them because of the lag between releases and updates of the package. This is also only my experience installing plesk on RH/FC systems. -- Michael Favia michael@favias.org tel. 512.585.5650 http://michael.favias.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Favia schrieb:
Gerhard Killesreiter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Karthik schrieb:
Page 5 on http://www.swsoft.com/r/pdfs/Plesk/plesk82_whatsnew.pdf
Does nybody know how the internals of Plesk work? Specifically: Does it have a push mechanism for updates? Or is it as uch a problem as fantastico?
Plesk runs an autoinstaller program that pings back to check for updates and notifies users with sufficient privileges upon login (namely admin). You can upgrade directly from the web administration panel but i normally find it best to run /usr/local/psa/admin/sbin/autoinstaller from CLI as root to monitor progress and catch errors as they happen. This update system really only affects Plesk packages and not OS packages. Frequent updates to the Application Library that contains the various installable Applications are available but i elect to just manually install them because of the lag between releases and updates of the package. This is also only my experience installing plesk on RH/FC systems.
Ok, so another fantastico disaster. Great news. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGl2ZAfg6TFvELooQRAiZ3AJ0VE3FYr0z5qAod1+Ymcn9RIqI4+wCfVDfk 6BqYAnINf/4Pahmys9lRPVA= =d+7E -----END PGP SIGNATURE-----
Ok, so another fantastico disaster. Great news.
Likely, but do not be so fast judging them. They can be responsible, taking the support load they incur and be fast about the security updates. If they won't, then we can always repeat what was done with fantastico...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karoly Negyesi schrieb:
Ok, so another fantastico disaster. Great news.
Likely, but do not be so fast judging them. They can be responsible, taking the support load they incur and be fast about the security updates.
Yeah. And distribute Ponies...
If they won't, then we can always repeat what was done with fantastico...
Did that help? Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGl302fg6TFvELooQRAr8CAJ4xQSIwZhB33H424GHYUDiJuD/YkwCgl30G F4PVRKyZ15P8dLzyd5Eiycg= =sMOi -----END PGP SIGNATURE-----
I think it is important to see a two-tier question on this: 1. In order to comply with expanding the term "drupal-user" to as wide-based a sector as possible, fantastico and plesk inclusion of auto-installation of drupal is a godsend, to help non-technical users _start using drupal_! 2. "We developers", on the other hand, who deal with multiple sites and version control with clients systems, etc, etc., etc., probably want to use SVN or CVS or other scriptly automaticated methods of handling our client's drupal installations. Any developer worth his white drupal dojo belt should have her own system of drupal site maintenance. And new Drupal modules are coming out to aid us in this. It is by the first and not the second criteria that we should judge this news, which, in the light of the first criteria, is good news. saludos, Victor Kane http://awebfactory.com.ar On 7/13/07, Karoly Negyesi <karoly@negyesi.net> wrote:
Ok, so another fantastico disaster. Great news.
Likely, but do not be so fast judging them. They can be responsible, taking the support load they incur and be fast about the security updates. If they won't, then we can always repeat what was done with fantastico...
Plesk is very finicky about the versions of software you install and very jealous of its own configuration file. So, once a server is running Plesk, it controls everything from Apache to MySQL to PHP. You can't modify a setting in Apache. Plesk will roll it back for you in few minutes. This means tuning things on a Plesk server is a pain. It also means you cannot upgrade things from RPMs, ...etc. While the motivation behind this is understandable (they own the configuration, so they only install their own sanctioned versions of the software and disallow you from changing it), it makes life so much harder if you want to upgrade something or install an accelerator, or tune something. So, this "fun" way will now extend to Drupal? Great. Means more headaches for the clients and consultants.
On 7/13/07, Khalid Baheyeldin <kb@2bits.com> wrote:
Plesk is very finicky about the versions of software you install and very jealous of its own configuration file.
<snip good characterization of Plesk> So, this "fun" way will now extend to Drupal? Great. Means
more headaches for the clients and consultants.
I still insist, this is not the case, in that we should not view one use case (non-technical person grabs hosting, chooses to auto-install Drupal instead of Joomla) with another (Drupal developer develops website as consultant, makes customized install of Drupal). These are different space and time use cases. For example, at least one of my clients is someone who first got turned on to Drupal via a fantastico install, then when I was contracted, of course together with the customer we made our own SVN based install. One thing had nothing to do with the other, in fact, client already knew about Drupal, accepted Drupal. On the other hand, if thousands of people start installing and discovering Drupal via their Plesk consoles, and set up simple sites, what's the problem? If a consultant runs into limitations they can either do a manual install or change hosting. A client can afford a separate hosting for a project: the cost of hosting begins to approximate zero, anyhow. saludos, Victor Kane http://awebfactory.com.ar
On Jul 13, 2007, at 7:39 AM, Victor Kane wrote:
On the other hand, if thousands of people start installing and discovering Drupal via their Plesk consoles, and set up simple sites, what's the problem?
For those without the "benefit" of experiencing the previous fantastico-related threads, the summary of the problem is: If Plesk doesn't keep the copy of Drupal they automagically install up to date, it creates support hassles and potential security problems for those of us who develop and support Drupal installations in the wild. For example, fantastico was still shipping 4.5.x core well into last year (or something insane like that). So, if Plesk keeps up to date, agreed, this would be nice. However, if they get it working with 5.0 and don't touch it for 2 years, it sucks. That's the worry. Only time will tell if it's actually a problem. Cheers, -Derek (dww)
A related point. I run a Drupal site on a server controlled by Plesk. But I maintain the Drupal site through FTP/SSH; I only use Plesk for db admin. I'll have to see if any changes to the new version affect my site. I doubt it, However. This would mean that you could still install Drupal "by hand" even if your host uses Plesk. We would just advise people of the alternate route if they have trouble. - Ken Rickard agentrickard On 7/13/07, Derek Wright <drupal@dwwright.net> wrote:
On Jul 13, 2007, at 7:39 AM, Victor Kane wrote:
On the other hand, if thousands of people start installing and discovering Drupal via their Plesk consoles, and set up simple sites, what's the problem?
For those without the "benefit" of experiencing the previous fantastico-related threads, the summary of the problem is:
If Plesk doesn't keep the copy of Drupal they automagically install up to date, it creates support hassles and potential security problems for those of us who develop and support Drupal installations in the wild. For example, fantastico was still shipping 4.5.x core well into last year (or something insane like that).
So, if Plesk keeps up to date, agreed, this would be nice. However, if they get it working with 5.0 and don't touch it for 2 years, it sucks.
That's the worry. Only time will tell if it's actually a problem.
Cheers, -Derek (dww)
So, once a server is running Plesk, it controls everything from Apache to MySQL to PHP. You can't modify a setting in Apache. Plesk will roll it back for you in few minutes.
To clarify, you can't modify a setting in the core httpd.conf of Apache, but you can certainly modify per vhost settings via Plesk's support for vhost.conf. I do it all the time. -- Morbus Iff ( softcore vulcan pr0n rulezzzzz ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus
On 7/13/07, Morbus Iff <morbus@disobey.com> wrote:
So, once a server is running Plesk, it controls everything from Apache to MySQL to PHP. You can't modify a setting in Apache. Plesk will roll it back for you in few minutes.
To clarify, you can't modify a setting in the core httpd.conf of Apache, but you can certainly modify per vhost settings via Plesk's support for vhost.conf. I do it all the time.
This is from memory (last year). We were changing the file called: /var/www/vhosts/example.com/conf/httpd.include (not httpd.conf) Trying to comment out safe mode and open_basedir: I recall getting a recommendation to change vhosts.conf, but not sure if we tried it or not. We have since moved to a non Plesk host, and like it that way. -- 2bits.com http://2bits.com Drupal development, customization and consulting.
/var/www/vhosts/example.com/conf/httpd.include (not httpd.conf)
Yes, that's wrong. That's Plesk's version. You want vhost.conf: [morbus@rm-1006-10 ~]$ cat conf/vhost.conf <Directory /var/www/vhosts/disobey.com/httpdocs> php_admin_flag engine on php_admin_value open_basedir none </Directory> ... -- Morbus Iff ( is this a cut out bath-poster Morbus, or what? ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus
Khalid Baheyeldin wrote:
Plesk is very finicky about the versions of software you install and very jealous of its own configuration file. True.
So, once a server is running Plesk, it controls everything from Apache to MySQL to PHP. You can't modify a setting in Apache. Plesk will roll it back for you in few minutes.
This means tuning things on a Plesk server is a pain. It also means you cannot upgrade things from RPMs, ...etc. This is an often misunderstood aspect of plesk. Yes the configuration files are autogenerated and replaced anytime a system configuration is changed but there is always a place for you to inject your changes in a way that lets them remain persistent.
* In the case of a global setting you just add a custom conf file to /etc/httpd/conf.d/ named anything.conf and it will be picked right up. * In thew case of a domain specific setting you create/edit a vhost.conf file in the sites conf directory. If you didnt know about these two insertion points i can see why ou might think plesk a pain but it really is a decent way to manage configuration files and allow custom modifications too. (This is not an endorsement of plesk as a whole). -- Michael Favia michael@favias.org tel. 512.585.5650 http://michael.favias.org
participants (9)
-
Derek Wright -
Gerhard Killesreiter -
Karoly Negyesi -
Karthik -
Ken Rickard -
Khalid Baheyeldin -
Michael Favia -
Morbus Iff -
Victor Kane