search

fureigh / drupal-open-referral

An oh-so-in-progress Drupal distribution for Open Referral/Ohana.
1 stars 0 forks source link

Set up Pantheon sandbox with this as the remote #3

Open fureigh opened 9 years ago

fureigh commented 9 years ago

Feel free to ping me if you have questions.

kaypro4 commented 9 years ago

@fureigh hmm, this doesn't look good.

https://pantheon.io/docs/articles/drupal/running-drupal-8/

I'll try forcing it and see what happens. :)

fureigh commented 9 years ago

Hmm. I think that just means they're not providing it out of the box because they're not prepared to support their customers through tons of changes. Importing an existing codebase should still work.

Whether it's a good idea to be working with Drupal 8 in its current state is a separate question, but: adventure ahoy! ;)

kaypro4 commented 9 years ago

@fureigh I tried the zip and upload method but no luck. And not error to go on. There doesn't seem to be a way to add an upstream until you do the initial site load so doesn't look like we can populate that way to begin. I submitted a support ticket so we'll see what they say. Keep you posted.

If that's a dead end, we can use my digital ocean server and just push to it directly. The plumbing is in place to autodeploy to here, I'd just need to create an account for you and you can use a password or generate ssh keys to make it easier to push. We can also look at other PAAS options too.

I'll keep you posted on the Pantheon option and we'll go from there.

kaypro4 commented 9 years ago

@fureigh this looks like it's the right info to get this set up:

https://pantheon.io/docs/guides/collaborative-development-github-pantheon/

I think I'll give this setup a go tonight. Keep you posted.

kaypro4 commented 9 years ago

@fureigh well, it's kinda sorta set up but I'm wrangling with the settings.php file right now. All was good until I added a gitignore file to pull it out of the repo (after I noticed there wasn't a gitignore) and when I pushed the update the Pantheon site went back to the setup screen. So seems that Pantheon wants the config files in the repo...lame.

I'm a bit concerned with that type of non-standard thing and their "don't worry we'll take care of you" magic behind the scenes. For example, they use this repo as their source for Drupal 8 https://github.com/pantheon-systems/drops-8 when the site is built and seems that it is maintained as the upstream regardless of what you do. And if I'm not mistaken we are getting updates from "Pantheon Automation" when they see fit.

Do you have any issue with me setting this up on my Digital Ocean server? It's a simple Ubuntu 14 server and I have it set up to deploy via git push. I think that having total control over all the moving parts will save us some headache now and down the line.

What do you think?

kaypro4 commented 9 years ago

hey @fureigh I just watched a Pantheon demo and asked about the custom upstream option and he said it's available if you do the free upgrade to an "agency account". Here's more detail:

https://pantheon.io/blog/building-sites-common-codebases-pantheon-one-agencies

Instead of getting (automatic) updates from their upstream in Pantheon we'll get updates from our github repo. Seems like what we're looking to do.

Do you want to go through the "Pantheon for agencies" signup form on your account and get the ball rolling?

https://dashboard.pantheon.io/organizations/create

kaypro4 commented 9 years ago

@fureigh sorry, me again....

So, one thing to watch out for I think is something I read into this statement on the site above:

"First, you need to create a Git repository which will be the source for your common code. The easiest way to do this is to just fork our starting upstream repository for either Drupal or WordPress into your own repository."

Does this mean that they have made some change to Drupal core to make it work on Pantheon? If so, that doesn't sit so well with me since we may end up chasing an issue down the line that was caused by their tweaks that aren't in core. So if we go this route, I think we should start with the d.org core and make any changes necessary there to make it run on Pantheon so at least we know where the changes are if they are needed.

fureigh commented 9 years ago

@kaypro4 Thanks for this! I'll go through the "Pantheon for agencies" signup and see how it goes.

As for the thing to watch out for: I'm not worried about it. :) I'm pretty sure they're just saying you need to have a Git repo, which we already do (here on GitHub). Let's plan to keep our codebase entirely separate from the D8 version Pantheon offers and just take it upon ourselves to apply updates as appropriate.

fureigh commented 9 years ago

Okay, I've signed up but it looks like I may need to take a slightly different approach (or total up the amount of business I've referred to them over the years ;) ). To be continued.

kaypro4 commented 9 years ago

Hey, someone inside Pantheon that may be able to help is Glen Cantrell. Since he's also on the OO leadership team: https://www.openoakland.org/leaders

Maybe we reach out to him if we need a favor. I was actually thinking that OO could have an agency account and we could operate under that. Might be tidy, be a good PR piece for Pantheon and provide OO with a Drupal platform that may get used for other things.

Let me know what I can do to help!

Matt On Jun 3, 2015 9:53 PM, "Fureigh" notifications@github.com wrote:

Okay, I've signed up but it looks like I may need to take a slightly different approach (or total up the amount of business I've referred to them over the years ;) ). To be continued.

— Reply to this email directly or view it on GitHub https://github.com/fureigh/drupal-open-referral/issues/3#issuecomment-108721186 .