Actively maintained

This module makes the lifes of webmasters a bit easier. We want to make it as easy as possible for Drupal end-users to have all the tools at a central spot.

Cache External Files module allows you to cache external files (like Javascript, CSS or any other) locally and then use these local copies. The local copies are refreshed by cron run - every file has expiration timeout that is checked and the file if refreshed if expired. CSS files are additionally parsed for 'url()' includes and any relative images are also cached locally along with .css file (so the path used in url() is still working fine).

Except JS and CSS files, you can use this module to sync some files (documents, images, etc) from centralized location (files should be available via http or https) - this way you will always have fresh copy of a file managed in central location.

Performance
It allows to have external files locally and use drupal_add_js and drupal_add_css to add local copies to your pages. Then these files can be aggregated and served as one single file along with all the other Javascript and CSS files.

Another consideration might be that if your site is really hitting the load then the provider of external files might not be able to serve the files as fast as you need them causing the users' browsers to load your pages longer (the use-case for this are different advertisements you put on the site).

Module development (Drupal 6 version) was sponsored by KM.RU.

Hosting Profile Roles extends Aegir to enable more control over what role(s) a client user is assigned during site install. Since, by default, Aegir client's are given UID1 during site installs, this module also allows UID1 to be assigned to another user. This allows tighter control of the client's user experience, and thus support for Software-as-a-Service (SaaS) type business models.

Current features

Additions to the front-end:

• adds a "Roles" tab to the platform page that includes (for each profile available on the platform):
  • a field for an Aegir user that will be assigned UID1 for sites created using that profile
  • a field for the name of the role to assign site creators

When a site is created on a such a platform:

• UID1 on a created site is replaced (in the site context) by the Aegir user specified on the platform's Roles tab for the relevant profile
• after the site is installed, a second user is created based on site's creator
• that user is assigned the role specified on the platform's Roles tab for the relevant profile
• the "Login" link is updated to point to the second user's account

用户可以用来申请密钥，然后管理员通过后台审核

This is an experimental rewrite of the project* modules for Drupal 7.

Have you ever what to control the access to a certain node or node group by Rules?