Useful things I just did

Environment setup for ssh stuff on my server. Eventually found and edited my bash_profile. Remembered how to vi and unix properly. Can't remember what I was originally trying to do.

Setting up SSH. Basic stuff. Understanding SSH.

Oh yeah, here's where I started, Drupal on Dreamhost.

/me clambers back out of rabbit hole to find a new one to explore...

oh, and adding an alias to my bash_profile alias ll='ls -la' for more verbose file listings. Cause otherwise I can't *see* .bashrc, say, without at least ls -a.

Crash course: clone local, push to server, bam, test site.

More or less. Reminder: Installing Drupal. Includes db setup.

Page two of install gives me "no data from server." ... what? the first page is fine, but I click "english" and it gives up? It's not even a WSOD!

Sweet bunnies. Upgraded MAMP, again, broke things. Eventually remembered to change my mysql password in /Applications/MAMP/bin/phpMyAdmin/config.inc.php (I had changed it away from 'root' at some point, for obvious reasons).

wooo finally got through the install script. Since I've only done core stuff before I don't really know what all I should use for a production site- username, site name, that sort of stuff. Just going to wing it.

So this is probably one of those stupid questions, but do I have to go through the install script every time I push up from dev to stage and prod?

So trying to push from my local dev environment to my test directory on my dreamhost server: fails, gives me a fatal, no directory, not a git repo message. I think I just had my ssh url written wrong, so switched from ssh://user@server/files/stuff.git to user@server:files/stuff.git and that seems to work. But now I'm not quite sure what that did for me- "This directory is not the working tree, where you edit and commit code. Rather, it is simply the central location for the git objects and history..." ok, so I still need to clone from there to test site. hm.

ok, so now that I'm drawn myself a nice diagram of where my branches and repos and whatnot are, plus associated dbs, I think I can keep moving along... somewhere I had a thing for using drush to keep sites synched... Can't handle adding that into the mix right now, just going to try getting my site up and running first.

With a little help from the git pages, cloning into mysite/test so I can try just a plain install on a live site with a real db. Then I just need to figure out how to pull the db back to local (I think an export will have to do for now, lest I find myself in hours of drush trouble).

... I should really probably be doing this with D7, not a totally random variety of D8. I'll just hit mysite/test and run through the install script real quick... My php installation is too old??? you can't be serious. *checks dreamhost info* ... php 5.2.17.

*Head-desk*

Nobody say anything. TBC after some coffee, methinks.

Useful bits of Drupal doc + site building init

Warning: contents are entirely stream of conscious/notes.

The best practices guide for Drupal has a lot of very important points to consider, but for my own technical edification, I'm focusing on just a few aspects. Handy list of core modules to become familiar with if not fully memorize, just so I grasp the breadth of Drupal functionality a little better. Right now I only know a few nooks and crannies! I'd love to do a big long workshop just to be taught, start to finish, how to build a basic site.

Read this next: Using test sites has some good starting points for setting up test environments, multiple servers, the sorts of things I need to be doing below (keeping test sites sych'd. synced? argh). I'll have a local install, then push to a test server (how to keep it private while being up with the same db/etc as my live site?), then from test to live. So the only problem is that my local dev env will be somewhat different from production. Forthcoming: post on Dreamhost's setup in relation to Drupal's needs. I've only posted my placeholder site up there with FTP and plain HTML files! No idea about dbs.

Ok, so. (don't even ask about that link, I don't know.) I want to actually develop my website. I want to do this with Drupal. Obviously.

Erm, or I could update my drush setup, instead. Went for a git repo this time, for my own sanity, but now apparently it needs something called Composer, too (Almost typed "composter." Guess where my mind is). I think it might be working now, hoping I don't really need to update all those php settings again. It's a wonder anything works, given how many configuration files I need to keep track of...

-Problem the first: Which version of Drupal? Do I go with D7 and have the benefit of contrib modules, established practices, lots of support? Or do I go with D8, which I'm at least as familiar with, probably more so, and get ahead of the curve and become more adept with what's to come? Keeping in mind that D8 actually incorporates bunches of modules that used to be in contrib, probably covering most of my immediate needs, but also keeping in mind that some things might still be broken, regular updates will be necessary, and the whole thing could break at any minute?

In my experience, breaking things is the best way I learn how systems work. Even though I know I'll have to rebuild bunches of times to compensate for my own learning and updates to core while it's in development, that will help solidify any new things I learn along the way. Too often I find myself figuring something out once, but then I don't run into the same situation again in my tiny bubble, so I forget it. Database setup, for instance. I need to get my head wrapped around how the DB works.

-Databases and test sites: Keeping local and test sites synchronized... using drush.
What is stored in the db? How does Drupal use its db? how is it accessed? Can I easily switch dbs? What would that be useful for? How do I move the live db back to stage and dev sites for testing? download a backup and connect? is there a faster way to get it re-connected, too? (drush!) Looks like I definitely don't want to use the same database for more than one instance of the site or I'll risk contaminating it with screwed up code. Probably reading the drush instructions for drush sql-sync will clear a bunch of this up.

What's a session variable, exactly? cookies?

Acquia cloud does this very nicely on its own with the drag and drop setup. Do I need a paid subscription to push to production? can I host my site somewhere that isn't Acquia and still use Acquia cloud? How much time should I spend playing with Dev Desktop?

What do I do on the backend v. the frontend? what will I use the CMS interface for, just content creation? Adding modules? Theming (this is a knowledge void for me right now)? Develop on a test, test the new thing, then install on the live site? What do I do frontend and what backend and then push? how much pulling should I do? I need to separate my creation phases (site building/dev and site maintenance/content updates)...

[TODOs are bold]

Becoming a Drupal Core Mentor

t's finally time to start doing something I should have done long ago: mentoring new core contributors! I've spent a small chunk of time as a mentee, setting up my own development environment (dev env), finding issues in the mentoring queue and on Drupal.org (d.o), and interacting with other core contributors. While writing documentation and doing rerolls has been a great way to learn Drupal, the real rewards have come from working with other contributors. It's been a great comfort to know that I can ask for help on IRC, and can always find a mentor online during the core mentoring office hours.

And the bonus is that teaching others is the best way (for me) to learn things! So I went to YesCT for some advice on where to start. Here are a few resources she pointed me to (in addition to this big page o' mentor resources):

First of all, the most important thing to remember for everyone in the Drupal community is that "we are all mentors." This blog post from YesCT is pretty much what I was trying to say in para #1, but she says it better. Being friendly is the best way to encourage new contributors to come back! See also: WebChick's comic about her first encounter on IRC with "the Drupal Community on a Bad Day."

Next we have a key component of being a mentor: reviewing new contributor's work. This requires knowing how to review the contributor's work, and how to review a patch itself (to check that it was done correctly). Sticking with the theme of constructive criticism, gentle reminders, helpful pointers and other supportive input here. Teaching contributors how to interact and communicate with others is a great way to keep everyone positive and engaged.

As a side project, I'd like to help update dm.o and d.o to merge issue task instructions with the regular issue queue, essentially add functionality to the d.o issue queue. Todo for me: read through these related core mentoring on d.o issues. I had just recently noted that having contributor task instructions linked on d.o as they are on dm.o would be much easier than googling them every time I start work on a new issue. Turns out there's an issue for that! (there's also a google doc I won't link to here, but, note to self...)

Then we've got resources for planning a sprint, which I'd really like to do at a Drupalcon in the near future, but am currently lacking a topic to sprint on. If anyone needs a sprint co-leader, I'm happy to help!

Part of sprinting of contributing is going to be getting everyone set up with a local environment to work with. At an event like Drupalcon, or even something on a smaller scale, this can become problematic if everyone is downloading new software etc at the same time. So here are the Drupal Community Tools Download Instructions (dctdi. Tech is almost as bad as gov't with the acronyms). We've also got an Austin specific Core Mentoring page here and of course the perennial dev env setup page here.

Phew. So far I've had a look at most of those pages, but I need to go back and read the issues for dm.o->d.o as well as go through the mentor resources links thoroughly. It's just really great to have a specific goal and project to work on! I enjoy contributing on issues, but with the current D8 beta push it's been hard to find anywhere I fit in lately. Tallyho.

One Week Website

ow, in all fairness, this was a very optimistic concept on my part. I can put together a decent looking personal website in a week, no problem. Getting through the entire process I've outlined below, blogging and documenting each step, including research, references, background, backend, comparison shopping, self-analysis and content transfer? Not so easy.

The idea, however, in documenting the entire process is that I, and anyone else who cares to poke around, can review my notes and see the progress I've made and the time/effort I put in to doing a relatively thorough job. Thoroughness might actually be a fault of mine. I have a need to understand everything about a topic, to understand how the wheel works before I drive the car, etc. I can't just install WordPress (WP) and go with it, I need to understand how the backend works, how my data and files are structured, how I can query that database, and why that form is the right choice for me.

This means my initial process is slower than would be ideal, but I think the payoff in the long run will be greater. I have learned to let some things slide for the time being, marking them to revisit later when I have enough background to understand them better.

First, I need to figure out how to track this list. Do I want to Gitify (version track) it? repost at the end of each sub-post? certainly link back to the original list with each execution of a list item. It seems like a version-tracked version I can update and reference would be best... without having to republish every time I make a change. So I'll have to embed the list (published github page) itself:

ps. Yes, this looks ghastly. I need to publish and then iterate. I hear this is a thing you do.
pps. I see the embed doesn't work in Google Reader. Will have to figure that out, too.

New Year, New Garden

fter a relatively successful summer of vegetables last year, this year I think I'll take a more studied approach. Well, somewhat more studied, really just building slowly on the last go-round and adding a few things. Mostly, I now have a large enough crop of compost to use for a bed or two, and I know how big those dang zucchini will get.

Unfortunately, this means I do need to dig a few new beds, possibly three or four. I already have a satellite view of the house to transform into a (to scale) chart of the yard in order to keep track of what was where which year. As most gardeners these days know, it's best to rotate which crop goes in what bed each year, so any pests don't get too cozy and the soil isn't depleted (can't find a good reference right now). I've heard lots of advice on keeping a garden journal of notes about each step of the process, how different plants fared, etc. Frankly, I didn't, it seemed like one more thing to do and for the first year, fine-tuning was not a big concern.

So, mapping aside, that leaves us with planning what plants and when. I'm still looking for a source for hops, sage and tarragon, seed or seedling, if anyone in the DC area wants to trade (I get most of my seeds from Johnny's Selected Seeds).

As you'll see below, quite a few things need to germinate indoors as long as eight weeks before the last frost (early April in Alexandria). My google calendar is now laden with "PLANT CANTALOUPE" and such. I'm going to try out a grow light this time as my seedlings got a little too sperky* last year, even on a South-facing windowsill. This does mean that I'll also need some sort of heat source underneath my seedling trays. Although the basement is a pretty regular temperature, it's only around 65F and seeds prefer something more like 68 or 70.

Anywho, I've put together this little chart for my own benefit, but thought it might be of use to some other backyard gardener. Feel free to copy the format or just get inspiration. Click the chart to see it full-size in google drive and to copy or peruse further.

*I grew up using this word and only recently encountered several people who said "What?! 'Sperky'??" It means what it sounds like. Don't suppose anyone else uses it?

Technical Testing Tribulations

ay back in November I finally staked my claim on a corner of the internet by registering and hosting a website under my name. I had stalled for almost a full year, thinking there was too much I would want to research before pinning down a registrar/host. Turns out that was the easy part (once I realised I didn't need a slew of dedicated servers in the former Soviet Bloc).

After choosing DreamHost at the recommendation of a friend and a popular website (Lifehacker, who recently re-affirmed DreamHost's dominance), all I had to do was learn how to code an entire website. And not just any website, one that would display a photographic portfolio dynamically and interactively and [buzzword] and [so on]. Ok, so I haven't quite gotten to that part yet, but the site exists and is a decent placeholder.

The holdup is that I'm the sort of person who can't just throw up something pre-fabricated and call it a day, I have to learn how to code the entire thing myself, learn databases and cascading stylesheets, from scratch. Maybe once I've done that I could take an easier route, but without understanding the background it seems too much like cheating. Besides, most of the point was giving myself opportunity to learn, given that my photos probably aren't going to start flying off the shelves (there are some up, but they, too, are placeholders).

So in the meantime I've just been using the web export feature in Adobe Lightroom (a god-send for those of us who like cataloging, integration with other applications and services and powerful but simple tools). The problem I'm leading up to is that I'd like to stop hosting the photos I use in blog posts on Picasa and move them all over to a dedicated storage folder on my website. Heck, someday I should move this blog there, too.

The problem is that to use a photo in a post, I need to have a link to the .jpg file that will never change, or at least use a relative link to just "/kitten.jpg" rather than "http:// blah/folderA/section56/kitten.jpg" and so on. So that's one solution. But I also need the photo to link to a gallery view on my website, so that the clicker can browse through other photos from my blog, and also use spiffy navigation controls to browse by keyword or just mosey back through other parts of my portfolio.

I'm not going to list how much of that I have no idea how to accomplish, because it's too overwhelming. But, I've written an entire blogpost about it now, so that will hopefully motivate me.

Oh, and the reason there are random photos of pie here is because they're hosted on my website, just... not very sophisticatedly.

...I flew a plane?

Looks like I neglected to post anything for an entire month despite the pile of saved drafts I have going here. eh heh.

A few years back I made a quick list of Life Goals for myself. Being in college at the time, they were pretty basic things: live in one place for more than four months (e.g. not a dorm), learn basic car maintenance, learn to fly an airplane.

Last Friday I made a step the right direction and took the pilot's seat in a Cessna 172 for a 30 minute flight over Gaithersburg, MD. Ok, I didn't entirely fly the plane, but it was pretty gosh darn exciting (and a little terrifying) to be steering a dinky aircraft at 2500 feet. The best part was takeoff. My co-pilot/instructor handled the throttle and details, while I pulled back on the yoke and actually got the plane off the ground. Causing yourself to suddenly become airborne is distinctly thrilling.

Anyway, as exciting as that was, the experience made it very clear how much there is to learn (and how much it would cost to learn it). As accompaniment to this adventure I've also been reading Beryl Markham's memoir, West with the Night. While it is ostensibly and primarily a book about flight, Markham also covers encounters with lions, racing horses and much else about living in Africa in the early 20th century:

Tom taught me in a D.H. Gipsy Moth, at first, and her propeller beat the sunrise silence of the Athi Plains to shreds and scraps. We swung over the hills and over the town and back again, and I saw how a man can be master of a craft, and how a craft can be master of an element. I saw the alchemy of perspective reduce my world, and all my other life, to grains in a cup. I learned to watch, to put my trust in other hands than mine. And I learned to wander. I learned what every dreaming child needs to know — that no horizon is so far that you cannot get above it or beyond it. These I learned at once. But most things came harder.

For a couple more photos, visit my picasa collection.

To think, to write...

Four years ago, I packed up my life and moved it all 500 miles to one small town on the top of a hill in Southern Vermont, without a damn clue what it would turn into for me. I may wax poetic about it all for years, in hindsight, in retrospect, whatever shades that might tint the memories. Everything wasn't always perfect, but the town of Marlboro felt like *home*. But before Marlboro, there was another me. A me who filled journal after journal with tiny cramped writing, drawings, designs, and lord-knows-what workings of teenage consciousness (the first image in this post is a quick view of some pages from an old journal of mine, and two books I hand-bound on the edges of the frame). Most of the writing probably isn't worth reading, but the way I lay out the text and sketches, sometimes weaving strands of text into images makes the journals visually appealing, a flip-book of nostalgia. Once I got to Marlboro I stopped writing and sketching after one journal of nothing but text. My question is, why did I stop? While I'm not prepared to completely answer that yet, here are some thoughts on the subject:

First, why did the content shift to text-only? Was it because I felt I didn't have the time to commit to more sincere creations on the pages? Because I felt my sketches and layout concepts were piddly, and not worth putting on paper? How could I be more self-conscious in college than in High School? My intent in keeping the journals was always that someday, someone would read them. Whether that would be a progeny or a historian, an alien anthropologist... Or maybe I thought they would fall into someone's hands sooner than that, and prove how awesome I was. With that in mind, I suppose the shift was because I started sharing more with people face to face at college, and didn't feel the need to record everything on paper for future transmission.

And then why did I stop writing entirely? Even at times when I could have used some introspection, I didn't write... at least not in paper journals. I began emailing, using Facebook and Twitter, recording my movements and thoughts in communications and snippets. Microblogging. This, so far as I'm concerned, is a significant step down. Maybe even a slide. Then again, I'm not sure all that introspection helped me develop much at the time, either.

I don't know if trying to restart my journaling is a mistake or not (my own version of NaNoWriMo... whatever month it may be). But if I think "nothing I do is worth recording, not the entire day, certainly" then I'm only discouraging myself. Maybe I became more private, in an odd, long-term way.

... and here I am blogging about it. Hopefully posting this will make me more inclined to journal at least once a week...

Wherein I wish I had better colour correction capabilities

A couple of weeks ago Marlboro VT had its annual town rummage sale. The first day, everything is for sale by donation. The second day, everything is free. There are two parts to the sale: the clothing and accessories, and housewares, which covers pretty much any random piece of junk you want to get rid of. So there I was, walking into the housewares section, located in the Town House (where Town Meetings are held each year), and lying plaintively on a table near the door was an open case with an old typewriter sitting in it.

Hello, the typewriter seemed to say. I'm old, and beat up, I could use some help, maybe a little love and a new ribbon. Just take me home, please? Don't leave me here...




Well. I browsed the rest of housewares for a while, and was leaving again when I felt its lonely little self reach out to me. Oh, all right, I said to myself, and bundled the thing up and brought it home with me. A girl and her Remington Rem-riter, a Remington Rem-riter and its girl. hm. I felt hugely guilty stripping the paint off of its casings, but I'm pretty pleased with the results. It also took a while.



The process included: dismantling the casing, unscrewing the carriage/ruler assembly, stripping the paint using a green stripper and a lot of patience, doing a coat of rustoleum primer, then a coat of copper spray paint, then some acrylic topcoat, dusting, wiping and oiling the insides, figuring out which pieces went where in what order (my notes were uniquely unhelpful), and finally, the test run. It still needs new ribbon, but it's damn shiny and happy looking now.














Somewhat ironically, or anachronistically, I don't have a printer, which leaves me without blank sheets of paper for my typewriter...

Whoa, Internet spaz-fest

It's always oddly awkward starting a blog. You have to find something enticing to draw people in, not over-do it, don't post every hour, get your formatting decent (without posting about what a hassle that's been)... So here I am, guys.
I'm also here:
Facebook (for RL friends only)
Delicious
Twitter
LibraryThing