7

Whenever a contributed module has a new version, Drupal's update manager will show a notification and allow automatic downloading of the updates. After that, the user is guided through "update.php". Is it possible to get the same automatic treatment for custom modules?

If I develop a few custom modules for a specific site, it would be interesting to get Drupal to look for updates of said custom modules, on a server specified by me, where I'm hosting the modules myself, and treat them like any contributed module. But maybe this goes against good practices?

Improve this question

1 Answer 1

Reset to default
4

maybe this goes against good practices?

Wouldn't have thought so, providing a central repo for your modules can only be a good thing in my opinion. It's the best way to keep multiple sites up-to-date with changes to custom modules.

What you need is a combination of the Feature Server module:

This module allows you to share features and custom modules on your own website. It lets you create projects and releases, and it produces an update XML feed compatible with the update module in core. In a way it's a highly simplified version of the project module.

And the project status url module .info file setting, for your custom modules:

Allows module maintainers to define a URL to check for updates to their module using the Update status module. No module released on drupal.org should define this parameter. URL should point to an XML feed that accepts requests in the form of http://my.domain.com/projects/{project}/{core}. In that example, project status url should be set to http://my.domain.com/projects.

Improve this answer
3
  • Feature Server has exactly the functionality I had in mind. Hopefully it will have a 7.x release eventually... Thank you.
    – CamilB
    Sep 16, 2014 at 12:02
  • It doesn't @CamilB, but you can use the D6 version to serve D7 modules - bit confusing but it does work :)
    – Clive ♦
    Sep 16, 2014 at 12:03
  • Yes, I had to read that part three times. But indeed... the D6 site should only care about the *.info file of a custom module (or not even care at all...), and won't actually enable the D7 modules it is serving to D7 sites. I'll look into it.
    – CamilB
    Sep 16, 2014 at 12:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.