any work done/planned on Drupal "HIBERNATION" feature
Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while? Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync ...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-) Best - Zeljko
I would add one other item. * a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode. Greg ________________________________ From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of zeljko blace Sent: Tuesday, August 21, 2007 11:15 AM To: development@drupal.org Subject: [development] any work done/planned on Drupal "HIBERNATION" feature Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while? Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync ...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-) Best - Zeljko
Actually, with a D5 / D6 site with aggressive caching and registration of members disabled, the load on the host is rather minimal. But such a mode could be interesting for an other application: backup. A site thus "hibernating" would not perform any data-modifying query. All insert/update/delete being frozen, including basic mechanisms like d5 watchdog/d6 dblog or accesslogs, a site could safely be backed up, which is not really the case currently. I explained it a bit on Larry Garfield's blog (http://www.garfieldtech.com/blog/drupal-7-database-plans#comment-369 ) ----- Original Message ----- From: "Greg Holsclaw" <Greg.Holsclaw@trouvemedia.com> To: <development@drupal.org> Sent: Tuesday, August 21, 2007 8:20 PM Subject: Re: [development] any work done/planned on Drupal "HIBERNATION"feature I would add one other item. * a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode. [...]
Site offline does that already, but makes the site offline (duh!) The code to allow admin logging in but not others could be reused though to do what you want without the site going offline. On 8/21/07, Greg Holsclaw <Greg.Holsclaw@trouvemedia.com> wrote:
I would add one other item.
- a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode.
Greg
------------------------------
*From:* development-bounces@drupal.org [mailto: development-bounces@drupal.org] *On Behalf Of *zeljko blace *Sent:* Tuesday, August 21, 2007 11:15 AM *To:* development@drupal.org *Subject:* [development] any work done/planned on Drupal "HIBERNATION" feature
Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while?
Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync
...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-)
Best - Zeljko
-- 2bits.com http://2bits.com Drupal development, customization and consulting.
Sorry, should have included 'while still making site content available'. This way you don't have broken links during the 'hibernate' period. The main use case for this is for when a site operator doesn't want to deal with the normal submissions users might make (maybe during a vacation or other leave of absence), as state during an extended backup/site move period. They want their site to be live, but not have submissions or other member contributions made (no database updates). So www.example.com/node/300 still renders, but /user/login is inactive/doesn't work unless you log in with the admin account. Greg ________________________________ From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Khalid Baheyeldin Sent: Tuesday, August 21, 2007 12:08 PM To: development@drupal.org Subject: Re: [development] any work done/planned on Drupal "HIBERNATION"feature Site offline does that already, but makes the site offline (duh!) The code to allow admin logging in but not others could be reused though to do what you want without the site going offline. On 8/21/07, Greg Holsclaw <Greg.Holsclaw@trouvemedia.com> wrote: I would add one other item. * a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode. Greg ________________________________ From: development-bounces@drupal.org [mailto: development-bounces@drupal.org <mailto:development-bounces@drupal.org> ] On Behalf Of zeljko blace Sent: Tuesday, August 21, 2007 11:15 AM To: development@drupal.org Subject: [development] any work done/planned on Drupal "HIBERNATION" feature Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while? Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync ...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-) Best - Zeljko -- 2bits.com http://2bits.com Drupal development, customization and consulting.
I wish it was as simple as /user/login. It is not. Users can have active sessions still, so something needs to be done about those. One approach is to log them off explicitly another is checking that they don't have some special permission (administer site configuration?) and treating them as anonymous users (fudge the $user variable?). Or maybe they still can browse the site as logged in users, but cannot create content or comment on content,. That is overly simplistic since there are many other things that are site specific that fall into that category (e.g. voting? userpoints? ...etc.) I guess there are many definitions to "hibernation" and they will be site profile specific. No one size fits all. On 8/21/07, Greg Holsclaw <Greg.Holsclaw@trouvemedia.com> wrote:
Sorry, should have included 'while still making site content available'. This way you don't have broken links during the 'hibernate' period.
The main use case for this is for when a site operator doesn't want to deal with the normal submissions users might make (maybe during a vacation or other leave of absence), as state during an extended backup/site move period. They want their site to be live, but not have submissions or other member contributions made (no database updates).
So www.example.com/node/300 still renders, but /user/login is inactive/doesn't work unless you log in with the admin account.
Greg
------------------------------
*From:* development-bounces@drupal.org [mailto: development-bounces@drupal.org] *On Behalf Of *Khalid Baheyeldin *Sent:* Tuesday, August 21, 2007 12:08 PM *To:* development@drupal.org *Subject:* Re: [development] any work done/planned on Drupal "HIBERNATION"feature
Site offline does that already, but makes the site offline (duh!)
The code to allow admin logging in but not others could be reused though to do what you want without the site going offline.
On 8/21/07, *Greg Holsclaw* <Greg.Holsclaw@trouvemedia.com> wrote:
I would add one other item.
- a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode.
Greg
------------------------------
*From:* development-bounces@drupal.org [mailto:development-bounces@drupal.org] *On Behalf Of *zeljko blace *Sent:* Tuesday, August 21, 2007 11:15 AM *To:* development@drupal.org *Subject:* [development] any work done/planned on Drupal "HIBERNATION" feature
Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while?
Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync
...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-)
Best - Zeljko
-- 2bits.com http://2bits.com Drupal development, customization and consulting.
-- 2bits.com http://2bits.com Drupal development, customization and consulting.
On 8/21/07, Khalid Baheyeldin <kb@2bits.com> wrote:
I guess there are many definitions to "hibernation" and they will be site profile specific. No one size fits all.
True - but I was referring to "computer" term hibernation - associated with Operating Systems - so no functionality at all but an option to "wake up" and resume normal functionality at some point. Maybe different needs could be mapped out and some scalable system designed based on that.
Simple answer: New permission "able to log in". To make a site "admin only" for a while, remove that permission from all roles, then only uid 1 can log in. Active sessions are easy: "DELETE FROM {sessions}". :-) --Larry Garfield On Tue, 21 Aug 2007 22:45:32 +0300, "Khalid Baheyeldin" <kb@2bits.com> wrote:
I wish it was as simple as /user/login. It is not. Users can have active sessions still, so something needs to be done about those.
One approach is to log them off explicitly another is checking that they don't have some special permission (administer site configuration?) and treating them as anonymous users (fudge the $user variable?).
Or maybe they still can browse the site as logged in users, but cannot create content or comment on content,. That is overly simplistic since there are many other things that are site specific that fall into that category (e.g. voting? userpoints? ...etc.)
I guess there are many definitions to "hibernation" and they will be site profile specific. No one size fits all.
On 8/21/07, Greg Holsclaw <Greg.Holsclaw@trouvemedia.com> wrote:
Sorry, should have included 'while still making site content
available'.
This way you don't have broken links during the 'hibernate' period.
The main use case for this is for when a site operator doesn't want to deal with the normal submissions users might make (maybe during a vacation or other leave of absence), as state during an extended backup/site move period. They want their site to be live, but not have submissions or other member contributions made (no database updates).
So www.example.com/node/300 still renders, but /user/login is inactive/doesn't work unless you log in with the admin account.
Greg
------------------------------
*From:* development-bounces@drupal.org [mailto: development-bounces@drupal.org] *On Behalf Of *Khalid Baheyeldin *Sent:* Tuesday, August 21, 2007 12:08 PM *To:* development@drupal.org *Subject:* Re: [development] any work done/planned on Drupal "HIBERNATION"feature
Site offline does that already, but makes the site offline (duh!)
The code to allow admin logging in but not others could be reused though to do what you want without the site going offline.
On 8/21/07, *Greg Holsclaw* <Greg.Holsclaw@trouvemedia.com> wrote:
I would add one other item.
- a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode.
Greg
------------------------------
*From:* development-bounces@drupal.org [mailto:development-bounces@drupal.org] *On Behalf Of *zeljko blace *Sent:* Tuesday, August 21, 2007 11:15 AM *To:* development@drupal.org *Subject:* [development] any work done/planned on Drupal "HIBERNATION" feature
Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while?
Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync
...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-)
Best - Zeljko
-- 2bits.com http://2bits.com Drupal development, customization and consulting.
-- 2bits.com http://2bits.com Drupal development, customization and consulting.
Yes just admin logon would be nice. I have a site for a conference that is finished. I don't want to spend any time maintaining it. The next conference is in 2 years and will be run by someone else. Meanwhile the email addresses of those who registered will be useful to them so I want the site to remain visible to the world. I will apply security updates to it but nothing else. _____ From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Khalid Baheyeldin Sent: Tuesday, August 21, 2007 3:08 PM To: development@drupal.org Subject: Re: [development] any work done/planned on Drupal "HIBERNATION" feature Site offline does that already, but makes the site offline (duh!) The code to allow admin logging in but not others could be reused though to do what you want without the site going offline. On 8/21/07, Greg Holsclaw <Greg.Holsclaw@trouvemedia.com> wrote: I would add one other item. * a way to turn off login except for the admin. This way you don't have to worry about member contributed content being added, without having to go to maintenance mode. Greg _____ From: development-bounces@drupal.org [mailto: <mailto:development-bounces@drupal.org> development-bounces@drupal.org] On Behalf Of zeljko blace Sent: Tuesday, August 21, 2007 11:15 AM To: development@drupal.org Subject: [development] any work done/planned on Drupal "HIBERNATION" feature Hi! I am developing a lot of small sites with Drupal with limited activity and would like to know if there were ever discussion or needs from other "deployers" to have their Drupal website HIBERNATE for a while? Good example would be websites that: * promote events and are active only just before/during/after event, while rest of the time they have no need for interactive features and dynamic content. Putting a static copy of website would not do it here as website goes back to active mode from time to time. * are temporarily without administrator/webmaster * that want to limit web use to a specific date/time to have people few people that use website come together on-line in sync ...hope this is not too strange and would resonate well with people who understand that web publishing could be more then networked-digitized print ;-) Best - Zeljko -- 2bits.com http://2bits.com Drupal development, customization and consulting.
Quoting Walt Daniels <wdlists@optonline.net>:
Yes just admin logon would be nice. I have a site for a conference that is finished. I don't want to spend any time maintaining it. The next conference is in 2 years and will be run by someone else. Meanwhile the email addresses of those who registered will be useful to them so I want the site to remain visible to the world. I will apply security updates to it but nothing else.
If you just want to control whether the site data is updated or not just modify the access to create and edit for authenticated users. You probably want to allow the user to update their profile data to keep email addresses up to date. There is also the node access module[1] that allows you to assign accesses to certain nodes based on role that may give you options. [1] http://drupal.org/project/nodeaccess Earnie P.S. This is a support list question.
participants (7)
-
Earnie Boyd -
FGM -
Greg Holsclaw -
Khalid Baheyeldin -
Larry Garfield -
Walt Daniels -
zeljko blace