Yak #1.

Why is my build failing?

Oh, sweet! JumpstartPro has a ci.yml specifying a github workflow set up for ci out of the box. But it's failing. Why?

Oh (forehead slap). Standardrb violations. I can fix that. Done. Green now, right? Wrong.

Yak #2.

Why is my build still failing?

Ah, there's an image file I referenced on a static page but forgot to add. Whoops.

I don't actually care about the image file right now but fine, in the name of a green build I'll go find it and commit it.

So, green now, yes? No. Dang.

Yak #3.

Why is my build STILL failing?

Ah. I put the file in ./app/assets/images but it's being served by a static file so it should go in ./public/images. Someday I will get all of the asset pipeline stuff straight in my head. Today is not that day.

So. Green now? Yes? Yes. But I have questions...

Yak #4.

First question: can I run the same commands locally that I ran in CI?

Nope. Getting a mysterious error. Oh, I recognize this one. It's because I'm running the wrong version of Node. Didn't I upgrade already? This should work? OK FINE NODE YOU WIN.

brew upgrade node

Run now please, yes? No. Denied. Same mysterious error. Why?

Yak #5.

What version of node am I running? 14? WHAT? How. Just...how? OH. Dang.

nvm use 18.13.0

So, it will run now, right?

No, now I'm getting postgres connection errors. Ugh.

Yak #6.

What's up with postgres? Oh, somehow something I did in the last hour killed my local server. OK fine, restart.

pg_ctl start

And now run. TADA! But wait...what are all those errors?

Yak #7.

The errors are from opentelemetry. I configured Honeycomb yesterday. Super easy! Super fast! Very cool! But I only configured things for prod, not my local env. And while I can imagine wanting to see traces on my local env, that's not a yak I want to shave right now.

So how do I only load opentelemetry in prod? (this is not nearly as irresponsible as it sounds...my prod is only used by me).

Ah, got it. Only config the sdk if Rails.env.production?

All green and clean now, right? No.