rupl / drush_make_generator Goto Github PK

For Drupal 6, the jQuery UI library was installed in sites/all/libraries/jqueryui/, but I think this needs to be sites/all/libraries/jquery.ui/ (the '.' is missing).

Instead of a web page, just serve the raw makefile.

Just noticed in playing with drushmake.me that when you select jquery_ui and friends, it doesn't automatically add the fetch of the appropriate libraries needed to the makefile. Shouldn't that be the default?

Please post in this issue to request modules or themes you'd like to see on http://drushmake.me

Original Issue:

I think Display Suite is getting more and more popular - can you add a section to it on the list? References (D7) and Fieldgroup (field_group) could be other candidates. Boxes is also missing, though I can understand that it might not be that popular. nowadays.

It would be great to be able to define a source of the module, library or drupal installation.

It could be a custom option in the select box that'll let you type in the source type and destination and branch if needed.

[UPDATE BY @rupl] Original title was "imce_wysiwyg invalid version option"

The only option for IMCE WYSIWYG Bridge is "1."

There should be 1.1 and 1.x-dev for D6, and 1.x-dev for D7.

High-level list of common websites, like e-commerce, social features, gallery, portfolio.

Picking an option should populate the generate form and allow for further tweaking.

Could work two ways:

1. Typing in a text box filters the list of modules until you find the one you want. Clicking on it wipes the text box to re-populate the list.
2. text box gets auto-completed from the existing list, and when you hit enter it checks that module's box

I feel drushmake is a little bit raw for everyday use (saving your module choices is the main stopper, i suppose). But I also know that sent patches is better then sent feature requests.
So... please update your drushmake_gen.sql to hold latest db dump with modules info, so I can add functionality and sent back patches

Please stop promoting use of the horrible v6.x-1.12-rc1 release, please replace it with 6.x-1.13. Also, please remove all v2 versions, they are currently unsupported and will probably be scrapped entirely.

hey, this is great !

have you considered making this a module for Aegir's hostmaster profile ?

version 1.0 of Aegir is released and there are some great possibilities

http://community.aegirproject.org/developing
http://community.aegirproject.org/node/33

Aegir is a great tool for managing distro's, but imagine the power of being able to actually create a distro from within Aegir? thats recursive bliss

-N

I chose Pressflow for the Drupal version and tried to make my custom installation however the URL for Pressflow was incorrect.

In the make file text it had git://github.com/pressflow/7.git however this didn't work properly so I changed the url to https://github.com/pressflow/7.git and all worked perfectly.

Allow tagging of shared makefiles to aid with #5 (suggested makefiles)

Currently only supports the basic makefile. A zip file option seems useful, for example when you request the zip it should execute the makefile on the server and deliver the zip after a few moments.

Option to request projects via git instead of contrib format (projects[] = XXX)

Hi rupl,

Great idea with a drush make generator. But you've got a bunch of notice errors in your code. Try enabling notice errors in your php.ini. Especially when your requesting variables through $_get or $_post that doesnt exits. You can use if(isset($_POST['foobar'])) { } to check if they exits. I can make a patch for you if you like.

Also i really dislike the use of globals, but that might just be me :)

would be handy to be able to check all and then de-select modules

I know thats overkill for production, but I am finding your tool to be useful education and time saver

gday rupl

I tried to select everything and make but the ckeditor module and the blueprint theme choke Drush Make

commented these out and it works !

THANKS AGAIN

-N

This should use the subdir config option for each module that has a patch associated with it in the makefile.

Can you update the SQL script in your github project with the current one you use on the site. I tried implementing this project with the current one and I had to add a type column to the version table just to get it from throwing errors. I suspect you're using something more current that you've posted.

Thanks so much.

Would it be possible to add a new section for patches? Something like the Library section perhaps?

Here's an example of how we incorporate patches now:

; Patches
; ------------
projects[drupal][patch][shibboleth][url] = "http://MYSITE/files/htaccessshibboleth.patch"

The URL could be anything; d.o., a blog, github...

Syntax from http://drupalcode.org/project/drush.git/blob?f=docs/make.txt

84 - `patch`
85
86   One or more patches to apply to this project. An array of URLs from which
87   each patch should be retrieved.
88
89         projects[calendar][patch][rfc-fixes][url] = "http://drupal.org/files/issues/cal-760316-rfc-fixes-2.diff"
90         projects[calendar][patch][rfc-fixes][md5] = "e4876228f449cb0c37ffa0f2142"
91
92         ; shorthand syntax if no md5 checksum is specified
93         projects[adminrole][patch][] = "http://drupal.org/files/issues/adminrole_exceptions.patch" 

It would be pretty awesome to keep track of patches this way.

Thanks for your consideration.

This should return a 400 header.

Bonus marks for http://sudo.drushmake.me/a-sandwich returning moshe's ASCII art from the drush example plugin

hi again

tried the D7 select all and got loads of problems, gave up on D7 using the generator (D6 works great however, so thanks)

; Generated makefile from http://drushmake.me
; Permanent URL: http://drushmake.me/file.php?token=77bf3b322972

cheers

-N

This is a great tool. Thanks.

I'd like to be able to re-generate make files with the same selections but with the latest recommended versions of modules, themes, etc...

Being able to return to a pre-populated form would be very useful.

In my use-case I just inherited a drupal 7.14 site and I've updated the modules with Drush. Next I'll make a new Drupal 7.15 platform (in Aegir) and migrate the site to the new platform.
It would be great if I could 'freshen up' the original make file before creating the platform. It's a good opportunity to add or remove modules, themes, etc...

Possible solutions may include leveraging what's saved in the database for each tokenized make file. Though; I don't know if that would translate to populating the form or not.
Or perhaps URL encoding the submitted form values to create a link might work too.
I'm curious to know what direction you'd like to go in.

In any case, the form would have to be updated to accommodate this.

I'd be happy to pull down a branch and contribute to a solution too.

Ther should be an option to exclude versions from make files.