Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.With the latest features, you can generate the feature module in the site code, if the server user has write privileges to that folder.
Lets figure out how we can use this to our advantage in DevShop!
Comments
Comment #1
ergonlogicWe can make the folder writable with a drush_HOOK_post_provision_verify(). But we'd only want to do this is development environments.
Comment #2
jon pughThat's a decent idea... however wouldn't it be better to use
drush_HOOK_pre_provision_devshop_commit()and thendrush_HOOK_post_provision_devshop_commit()so that we can make the permissions secure again, and so that it runs on the right task?Comment #3
jon pughThis will probably be solved by adding the ability to stop the pull queue, and the ability to edit and commit directly on the server.
However, the features module requires you to set more lax permissions on the folder, so this is a tricky problem.
Postponing.
Comment #4
jon pughThis will be complex...
Possible workflow:
1. User visits feature rebuild page. Clicks "Generate feature" which sends a message to devshop to run the feature rebuild task, along with the info file. A message is displayed that their feature rebuild has been queued in devshop.
2. DevShop's Webhooks module receives the info, and starts the task.
3. The task writes a new info file, and runs drush features-update, commits and pushes the code.
Comment #5
daggerhart commentedIssue queue is now mantained at Github.