Did not have a productive morning, but did have good conversations! Also had delicious food from Jess, who appears to have become my food fairy this week. She brought lentil taco fixin’s on Monday, some gingerlicious garlicky shredded beet salad yesterday, and herb-crusted tofu + pesto + avocado sandwiches today, plus cupcakes. The latter was the result of me stating that most of the grief symptoms were mellowing, and my feelings were starting to have shapes again, except I kept not being hungry and/or forgetting to eat — so she asked me what I liked to eat. And you know, I still love good sandwiches.

Went out with walkgroup, partly because walks are good, and partly because April’s leaving a little early (today!  🙁 ), and we quested in the streets of SoHo with a GIGANTIC RC contingent, and it was amazing.

Came back and continued grinding on my Twilio/Heroku tutorials. The Twilio tutorial is so rad, and then you get to this point:

At this point in the tutorial, you will need to find a way to expose your server to the public Internet.

Here are some tutorials that may be able to help you:

[…]

For the rest of the tutorial, we will assume your server is available at example.com.

Which, to me, sounds like, “I know you came here to learn things by having them explained, and that’s been going really well, but I was thinking you could just, like, go do a internet at yourself if that’s cool. kbye.” (Me: “no, I’m not sure that is cool, but let’s find out.”)

I am sure that if you are a 1337 web h4x0r type person, this all sounds awesome and simple, but also probably you are not following along with a beginner’s tutorial. This plunged me into the glorious deep end of Heroku resources, and spinning up dynos (what even is? not yet totally sure, despite reading about them), and I have a bunch of tiny apps locally and on Heroku that do tiny little things, and it’s kind of neat. The challenge is just how to blend them together.

As a side note, Heroku and Twilio also have different guidance about how to create a new virtualenv, so that’s interesting.

Heroku suggests `virtualenv venv` for the initial setup, and then `source venv/bin/activate` to start things up each time.

Twilio, meanwhile, suggests `virtualenv –no-site-packages .` for the first part, and then `source bin/activate` thereafter.

Who is right, in this battle of style? One of them is easier to set up, from my perspective, and one of them is easier to run each time you’re working.

Finally, I had both an independently successful Twilio test app, plus an independently successful Heroku app, and put them together…and a spectacular fire resulted.

I persisted for a while, and eventually ran into this:

$ heroku logs --source app
 !    Internal server error.
 !    Run `heroku status` to check for known platform issues.
$ heroku status
Installing plugin heroku-status... done
=== Heroku Status
Production:   No known issues at this time. 
Development:  No known issues at this time.

Doubting that this was right, I ran it again:

$ heroku status
=== Heroku Status
Production:   Yellow 
Development:  Yellow 

=== Potential API Issues 8:59:15 PM UTC (https://status.heroku.com/incidents/797)
[Investigating] 8:59:15 PM UTC (less than a minute ago) 
Our automated systems have detected potential issues with the API.  We are investigating.

Updates were swift and helpful, but once we hit this one:

Until this API issue has been resolved, you will be unable to log into your Heroku account and unable to contact support.

I gently flipped the table and decided that was a good signal to head out to the LEGO store to meet up with Ann and Steven.

Beyond “time spent with Ann and Steven,” here are two more reasons this was awesome:

I also picked up the positively gorgeous LEGO birds set, which was one of those “vote on the things online and then maybe we’ll make it into a thing” projects (LEGO Ideas). This might be the first actual “make some particular things” LEGO set I have ever owned. Not just as an adult — ever. (For the purposes of this sweeping statement, we are ignoring the giant box of assorted plain LEGO I bought myself as a college freshman, and also the rad Klutz book with a packet of awesome parts, because those didn’t build A Thing.)

I am THRILLED.

As a side note, you may remember another LEGO Ideas set, the Research Institute, which featured a bunch of women casually doing science, but which now has a note about how it “was overwhelmingly popular and is no longer available for purchase.” Do the LEGO people not understand how capitalism works? You can continue to sell popular things in exchange for money.

Outside of LEGO adventures, this week is full of feelings, because the summer 1s continue to have ever-decreasing amounts of RC time left before they Never Graduate. FEELINGS.

 

Spoiler alert: Thursday I get Twilio + Heroku = <3, with excellent help and encouragement from Steven.