Packaging & Deployment
This group serves as a central point to allow for the coordination and informal discussions amongst the developers of several modules that have similar and/or complementary functionality, allowing us to reduce the duplicated code bases and more easy leverage each other's solutions.
The goal of this group is to put together a set of 'best practices', that allow for the easy integration of all these modules, and the education of these best practices to the contributed module developers, so that the resulting system can provide a solid platform for resolving the packing and deployment problems we are faced with.
A way to synchronize settings using features?
I've just stumbled into features / contexts recently and it is simply awesome.
I am wondering if synchronization of settings are possible using features / context?
I have a test machine and a deployment machine, where files are synchorinized using a git.
i'd like a way to easily synchronize menu settings, example i use the admin module and enable / disable menu items's visibility. Also, i change the input filters settings. Now to migrate those to production machine, have to manually do everything.'
What techniques do everyone use for such tasks?
Bibek Shrestha
Groups, Spaces, Context, Features...Do I need all those?
I'm building a website that consist of a main website and three office locations/branches websites. The main website pulls content from all three locations.
Location websites must have a 'home page' with a unique url, as well as the main website ofcourse. Each location must have an allocated admin role that can manage that location content only.
Why not make installation profiles full-blown modules in D7?
I really like that in Drupal 7 installation profiles will be treated as modules. However now that I started thinking about actual implementations, I'm wondering why they are not actual modules. For instance with DrupalMU the required modules and settings could be deployed both at the moment of installation as at a later date. The required modules and the function calls however would be identical in both cases. So what do I do? Do I make it a module that has a .module and a .profile file that works when dropped in either the sites/all/modules or in the /profiles directory?
Drupal Theme Designer/Graphic Designer | Fie.nipa Group
An experienced Drupal theme designer with usability experience needed to build a custom theme for an e-commerce portal.
Build group features of modules that does not use views?
Hia, sorry if this is a stupid question, but I'm struggling to build (OG) features of modules that does not use Views, as I do not know how to filter for Space without Views.. With Views you select the spaces filter, and set for instance "show nothing" when node is not in space.
But, what if the feature I wish to build does not use Views? Am I out of luck?
Intgreate Features Server with Atrium,Case Tracker
I was playing around with integrating Atrium and the Features Server feature and thought I would share my basic process. This is in no way perfect but it's a start. Please add on other useful pieces of information.
Export/import content with Features
Hi all,
I’m planning to contribute a module which will offer nodes import export capabilities for features, let me know what you think about it, if it makes sense to have something like this etc...
Here its description:
Features Content
The module enables Features to export/import nodes objects (along with their files, menu items and CCK fields) in a feature package. For each feature it is possible to decide which node to export (based on its NID, type, etc...) and if to keep its NID or to recreate it from scratch to the next feature import/update. For the moment authorship export is not supported: all the imported nodes will inherit a common user UID (configurable) if their own is not present in the system.
A critical look at the implementation of Plugin Manager - Underlying issues and possible solutions
I have been harboring some growing concerns about the direction of the plugin manager integration proposals for Drupal core almost since their inception, but have not been able to make an informed opinion on the subject until I had properly reviewed the proposed system on a much deeper scale.
While my impressions of the project and the current implementation are fairly negative, I have aimed to frame my criticisms in a positive constructive manner because I believe that the goals of the project are worthwhile, and that for a large section of users this could be a very flexible and usable solution.
Unfortunately a lot of my concerns have been well founded, and I believe that the implementation of this system needs to be taken in a different direction for it to be able to succeed in its goals, while not negatively affecting projects like Aegir, Open Atrium and many other ‘serious developers’.
Features / Spaces / Context Questions
Hi there
I've been trying to get my head around Features / Spaces / Context today, and although I know it really excites me, I'm not sure what else I know about it!
If I got it right, then this is what the three modules are all about:
Context: Let Drupal know you are in a particular area (eg blog) and change settings depending on where you are (eg change active menu, show different blocks)
Features: Lets you export and enable exported features, created mostly with context.
Packaged features for download?
Just watched this screencast http://www.developmentseed.org/blog/2009/may/29/making-and-using-feature... and am really amazed by this.
Is there any place where features (not the module) can be downloaded from? To be able try this out with something like that Discography feature would be great.
Aegir code (and drush!) now accessible through git
I have finally got around tackling git-cvsimport. After a little bit of tweaking around, I've been able to import the entire history of the various Aegir projects on Drupal.org in our git repositories. This will enable much easier collaboration and decentalised development.
Tell Us How Drush Has Made Your Life Easier and Get a Free Shirt
To celebrate the launch of Drush 2.0, we’re handing out several I <3 Drush t-shirts.
If you want a shirt, what you need to do is make a screencast or blog post about how Drush has made your life easier. Show or explain how you used to do something manually, and how it’s much quicker and simpler with Drush. Once you’ve posted about Drush, tweet about it with the #drushrush tag, and we’ll select the top three posts and those authors will receive a t-shirts in the mail.
So start posting and happy drush’ing. Oh yeah, you can also buy the shirt over here but what fun is that.
Posted some details on building installation profiles
For anyone who attended the Florida May meeting where I presented a case study on my work for ScubaDiving.com, which focused a lot on installation profiles.. well I finally posted some details on my blog on how I built it, along with some related details:
http://www.mc-kenna.com/drupal/2009/06/building-drupal-installation-prof...
Please post comments on my blog if you have any feedback, in the interests of keeping the discussion centralized.
Do you test new modules before uploading them to your live site?
Aegir 0.2 release candidate 1 released.
We're proud to announce the first release candidate of the 0.2 release of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This release is the first release candidate of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has been focussed on improving some our experimental multi-client functionality, as well as fixing bugs for our final release.
Aegir is in code freeze, and only bug fixes and usability improvements will be allowed in. The final release of Aegir will occur shortly after the 2.0 final release of Drush, and we will only be making changes to Aegir to maintain compatibility with Drush upstream.
Aegir 0.2 beta 1 released.
We're proud to announce the first beta of the 0.2 release of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This release is the first beta release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has also primarily been focussed on fixing bugs and polishing the final release of the 0.2 release.
Aegir 0.2 ALPHA 1 released.
We're proud to announce the first alpha of the 0.2 release of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This release is the first alpha release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has also primarily been focussed on improving and simplifying the back end system, by incorporating a lot of our custom API's upstream into the Drush 2.x project.
Update: Check out this screencast for a quick walkthrough of the features available in this release.
Drupal 'ports' collection
What is it?
My recent work on Aegir has been very deeply oriented with Drupal package management and dependency checking.
From the perspective I have been working from (unix command line scripts), the currently existing functionality of the update module is simply not useful.
I am in need of an easily mirrorable meta-info repository of all the drupal projects, and all the drupal modules. I need to be able to figure out dependencies
Exportables module
Yesterday I released the exportables module, which allows views-style exportables on objects which normally can't be exported (because of a lack of machine readable name). Currently, I've implemented taxonomy vocabularies, but more are planned -- add your own ideas in the comments for what I should make exportable next. Vocabularies are implemented using this code -- http://pastie.textmate.org/437640. Currently, there is no features module integration, however I'm working on that.
mentors for a patterns like module builder
There is a GSoC proposal at http://groups.drupal.org/node/20917 that you should check out.
In short it's a patterns-like module that can be used to build modules. It could help a lot to speed up the development of little helper modules that projects often need (e.g. to add a little extra functionality, but that are not contribution worthy).
Tamas, has been a trainee for almost a year now at our company and I'll be his "local mentor" for GSoC.
He would still need co-mentors with relevant technical background. Anybody interested?
