part one of this tbd series deals with starting a brand new install from scratch on pantheon, or migrating an existing site (local or remote) onto patheon. but first:
a brief foray into pantheon terminology
pantheon has three main ways of categorizing your wordpress build. two make sense.
code: your entire file structure of your wordpress directory. basically everything except the database. oh, and, somewhat inexplicably, without the uploads* folder. you’ll need it, but i’ll get to that.
*located at wp-content/uploads
database: er, yeah, the database, in the form of an SQL dump.
files: here’s where it gets a little weird. for reasons that my cursory googling could only partially figure out (storage, size reasons), pantheon keeps everything normally in an uploads folder in a separate root directory called “files”. so that’s a thing.
disclaimer: i started writing this in december and then realized it was a lot more information than i thought (mo’ files = mo’ problems). so i split the info into three categories, but i haven’t written the latter two yet. the first is mostly ready so should be out soon. skip to part one
for the past three months, i’ve been using pantheon.io for my development process making a relatively small but almost entirely custom wordpress build. pantheon specializes in hosting and managing wordpress and drupal sites, and for me was mostly a good experience. for some quick tl;dr:
Git integration and insta-repo — push changes right from command line or your preferred Git client
handles all of your server needs and maintenance
somehow free for the first 15 sites
relatively easy to initialize and go between dev and testing environments (with a few caveats*)
one-click backups per-environment
setting up locally is a bit of a pain and docs are outdated
if you are migrating a large site, gear up your command line skills and pat yourself on the back for good luck
exporting a large site for the first time is similarly awkward
not really sure what’s happening with the database unless you export the whole thing and look
the git/sftp toggle makes updating wordpress & plugins a pain
if you’re not sticking with pantheon for the entire dev to live process, it can get a little…awkward, shall we say.
in the upcoming articles, i will (hopefully) outline:
starting from scratch on or migrating a site to pantheon
developing with pantheon
exporting a site from pantheon
note that this article assumes a basic understanding of source control (specifically Git) and wordpress, and that i develop on a macbook pro so most of this will be with os x experience.
so a few days ago i actually purchased an app. for the first time ever. (some would say i’m cheap, but i prefer frugal)
what warranted the opulent purchase of $3.99, you ask? Tasker, the android automation app that apparently lets you automate just about everything on your phone. i was instantly enthralled, to say the least.
i’m still new at this, but today i figured out how to display something pretty nicely and i couldn’t find the instructions on almighty google, so i’m sharing:
how to make an at least semi nice looking active profiles display widget
if you haven’t already guessed, i’m going to provide a short tutorial of how to get the “Active Profiles” custom widget seen in the screenshot. you may also be wondering why on earth i’m still using BBM, but i’m going to ignore that for now.
why yes, i have been googling that for hours, thanks for checking. but since Zooper is $2.99 and i’ve already indirectly mentioned that i’m a fan of free apps, i wanted to see if i could do this with Minimalistic Text instead. so i did.
it is important to note that when Tasker Profiles become Active (in use and lit up green within the app UI itself), Tasker stores a comma separated list (a string, not an array) of all of the Active Profiles in its built in global variable%PACTIVE. they also put commas at the beginning and end of this string “to make matching easier”. it is very ugly. this will come up later.
i’m in class today, so a lot of these helpful hints have to be attributed to my professor, Andrew Smyk.
today we’re talking about how to get your website noticed and up to responsive web design standards. my professor purposefully broke his website and made his code terrible as a teaching tool. a pretty effective tool, at that. it’s like a scavenger hunt for bad code!
anyway, here are some dos and don’ts for all of your beautiful webpages:
DO: a favicon. let me repeat that. a favicon. apparently this will increase clickability in the browser by 50%. you know how when you have a bunch of tabs open you’re more likely to go back to the tabs with pretty pictures instead of a nondescript blank page icon? yeah. that.
Hey there! You’ve found my intro to CoffeeScript page. You can learn CoffeeScript at the same time I do! I’m no expert, but I’ve learned a few things and thought it would be good to share. This is my beginner beginner’s guide.
This tutorial will include written explanations and demo videos. They will be divided into sections based on themes in CoffeeScript. This was my first time uploading videos and I couldn’t figure out how to edit them without majorly decreasing quality, so unfortunately to strike a balance they’re a bit blurry. Any helpful hints would be appreciated!