I don't really want the repository update to require any interaction......is there anyone that does? I think it would be fine to have cron handle it....

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

That seems reasonable, but since it does take a long time to run perhaps it should be "on cron but not more often than every 12 hours" or something like that.

I believe the update_status module follows that practice of doing it on cron but not every cron.

jabapyth’s picture

jabapyth commented

that makes sense

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (won't fix)

When first installing a website, this would be useful, but after that I believe that it would become a liability. Since (at least for non-developers) installing new modules and themes does not happen very frequently, that bandwidth (both from d.o and the user's websites) would be wasted most of the time.

Also, I can't help but wonder what would happen if large numbers of Drupal installations all attempted to download somewhat large files from d.o every serveral hours.

Lastly, at least personally, I don't set up cron until after I've installed the site, theme and a few modules. By that time an automatically updating repository would be of no use.

And as far as for checking for updates: we call functions from the update module for that. Thus, our repository does not affect the update module's repository.