You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
Hi, I'm new to Pantheon platform and trying to configure Drupal 7 composer based project using this example repo and I'm almost on the verge of losing my nerves. It's incredible how much energy I have to invest in order to set up a fucking development environment.
Question_1: Are deploy_products scripts missing?
Question_2: How to configure correctly workflow hooks?
Following the next steps, I managed to configure Drupal 7 development environment (locally that's exactly what I want):
The problem arises when switch from SFTP to Git mode, files that are created through the composer are lost and that would not be such a problem that Pantheon runs composer install or update after code sync or deploy.
What I'm expecting is to develop custom modules or themes in Git mode, to push changes to the repository which will automatically be deployed to Dev but at the same time to use composer to manage Drupal modules and their dependencies.
Why this is so complicated or have I missed something? What would be a normal workflow that I feel comfortable as a developer, but on the other side to respect Pantheon rules, that we do not get into the situation to have conflicts when using update button on dashboard etc? Maybe to pull custom modules and themes also through composer as separate projects?
Thanks in advance,
Vladimir
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm new to Pantheon platform and trying to configure Drupal 7 composer based project using this example repo and I'm almost on the verge of losing my nerves. It's incredible how much energy I have to invest in order to set up a fucking development environment.
Question_1: Are deploy_products scripts missing?
Question_2: How to configure correctly workflow hooks?
Following the next steps, I managed to configure Drupal 7 development environment (locally that's exactly what I want):
// Create sandbox project
$ terminus site:create my-site "My Site" "Drupal 7"
// Clone D7 or D8 composer based repository
$ git clone https://github.com/pantheon-systems/example-drops-7-composer.git my-site
$ cd my-site
// Remove git history
$ rm -rf .git
// Recreate repository
$ git init
$ git add -A .
$ git commit -m “Initial commit.”
// Switch connection mode to Git
$ terminus connection:set my-site.dev git
// Push repository to Pantheon
$ PANTHEON_REPO=$(terminus connection:info my-site.dev --field=git_url)
$ git remote add pantheon $PANTHEON_REPO
$ git push --force pantheon master
// Run composer install
$ terminus connection:set my-site.dev sftp
$ terminus composer my-site.dev install
// Instaling Drupal
$ terminus drush my-site.dev -- site-install --site-name="My Drupal Site"
$ terminus dashboard:view my-site
The problem arises when switch from SFTP to Git mode, files that are created through the composer are lost and that would not be such a problem that Pantheon runs composer install or update after code sync or deploy.
What I'm expecting is to develop custom modules or themes in Git mode, to push changes to the repository which will automatically be deployed to Dev but at the same time to use composer to manage Drupal modules and their dependencies.
Why this is so complicated or have I missed something? What would be a normal workflow that I feel comfortable as a developer, but on the other side to respect Pantheon rules, that we do not get into the situation to have conflicts when using update button on dashboard etc? Maybe to pull custom modules and themes also through composer as separate projects?
Thanks in advance,
Vladimir
The text was updated successfully, but these errors were encountered: