I’m not talking about no chinos, rather setting up a Docker Container. Gotta get this together as a part of the whole dev workflow, containerizing the entire environment, for deployment in AWS or other server/ clouds.
Building out to the proper workflow from the top down , I’ve been building up the local dev environment in the Mac’s MAMP:
Added Composer and then Drush with a minimum of fuss.
Getting git to go required an additional slapperdoodle.
As I mentioned last time, the right way to manage core and module updates is through Composer. So, here’s what I done did:Continue reading “Starting from Scratch, with Composer”
So. I can’t just drop composer on top of a Drupal site, it must manage the site from the get go? srsly? And to be fair, this Drupal AND DB both originated from a godaddy install-a-tron, so maybe there’s a load of GD cruft in there which would be good to git rid of. And I did’t really drop in much content, at least that wouldn’t kill me to lose, but I really don’t wa-a-a-a-nt to build a new site for each. again.
A post unto itself. I thought I could wing the Composer commands and bam like
composer update drupal/core --with-dependencies
but, no. 500 errors, drush didn’t think there was a site there, and I had to start over from
git reset --hard origin/master
If you have not installed Drupal 8 using composer, you have to convert your site to a composer managed project to be able to update Drupal using the commands above. See “Add Composer to existing sites” for a step by step guide to manually adding composer to existing Drupal 8 sites that were previously installed without Composer.
well, ok then. not tonight tho
Having one complete dev > stage deployment under my belt, I’m going to do the following to prep for a full production deploymentContinue reading “And with that, Victory!”
So, I had all day confusion, yesterday, as to why my newly git copied site wasn’t working. I had the settings.php right, I had the .htaccess set up, copied over the sites/*/files, I was sure of the DB connection, but Drush didn’t recognize the new Stage site. And, this /vendors/ folder was missing. which WAS in the .gitignore. But once I copied the folder over, BAM site up like nothing ever happened. So what gives?Continue reading “Git Deploy & Composer”
Working through structuring changes to the properties of people, places and things over time captured as events, it dawned on me the changes themselves should be encapsulated and codified by Actions, rather than exposing the raw Object/ character values for direct manipulation.
More about Actions:Continue reading “The Floating Lands: Actions”
Its time to revisit Cloning my Site, now that I have access with the command line tools, and Composer, Drush and Git installed. I’ll do Stage >> Dev, as I haven’t touched Dev at all yet.
So, change of plans: Stage was not prepared to be cloned yet, both the docroot and the config ought to really be contained in their own root folder for a nice clean git init. I will manually copy using unix command lines instead of git into a nice isolated Dev folder set, THEN git clone from Dev into a re-built Stage, and then >> Prod, if that was successful.
Oh man! oh man! I just installed Composer (I think its just an installer… thing?) and Drush!
Using git to git following https://duntuk.com/how-install-drush-godaddy-cpanel-hosting and also https://duntuk.com/how-install-composer-drush to git it all in there.
BAM!!!!!Continue reading “Composer! Drush!”