Task #676
Task #541: Set up Apps server
Split off separate Git repos for each feature onto Github
| Status: | New | Start date: | 05/09/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Sam Boyer |
% Done: | 0% |
|
| Category: | dev | Spent time: | - | |
| Target version: | 0.2 |
Description
In order for the Apps server to function properly, it needs to be tied to features which are in self-contained Git repositories. So I'll filter-branch out each of the repositories, drop them on Github, and the features server can pull them from there.
We'll need to sort out the proper procedure for working with them in the dev environments...
History
Updated by Andrew Mallis about 1 year ago
A suggested workflow for local development is to put features them in a multisite, like so
sites/fga-events.local/modules/features
and have a gitignore policy in the user's home folder: ~/.gitignore
to exclude the local site (see the developer guide)
Drupal will give precedence to features here over sites/all/ which means you can work on these local features, commit them and push up to their individual repos without affecting the main stack.
Then, on the Pantheon DEV environment, features can be updated using drush aliases, i.e.
$ drush @fga-events.dev -y upc my_feature
IF on-server development is turned on. A commit message can be written from the Pantheon interface.
Alternatively you could also have a second site with no features in it like
sites/fga-events-pull.local
and cd into that, clear cache and drush update the features that are in sites/all
Updated by Sam Boyer about 1 year ago
i tend to think that representing different environments using multisite is The Wrong Way, as i've said. but until i have and have documented a better suggestion, i'll shut up and ponder.