@skyfaller @alexhillman there is no credible Republican candidate for any Philadelphia office. The working families party should run candidates, because they could become the second major party in the city.

@bethsawin three sisters farming method

LOL literally was a two line change. Thanks XHTML, you were awesome.

Ok now that I have jekyll working, I suppose it's probably time to move from XHTML 1.0 Transitional to HTML5

@inkypitchbot

Hey this one is actually pretty good

I forgot how much fun using Jekyll is, and how easy S3 static site hosting makes everything.

I couldn't resist putting "Latest toots" on my homepage where my mastodon feed is embedded.

Thanks to https://fedifeed.com/ for the embed code!

Having fun reading

https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/oxX69KFvsm4/m/WJXUELicBQAJ?pli=1

On the same day the Inquirer reports on how corrupt, FOP-chosen doctors put hundreds of cops on disability with full pay, WHYY reports that FOP President John McNesby is on Democrat Josh Shapiro's transition team

https://whyy.org/articles/pa-governor-josh-shapiro-transition-team/

In the end, I said fuck it and pushed the _site directory to my S3 bucket and hoped for the best.

Thankfully, it just worked. Who knows if there are any regressions. I know I made some major changes to the site and templates to make it work with newer versions of Jekyll, removed a bunch of plugins that no longer work, so some pages may no longer look as nice as they should, but at this point it's time to at least push the site and accept whatever breakage happens

It was kind of a nightmare using cygwin. Ruby 2.3.8 wouldn't compile correctly, and Ruby 3.2 made some breaking changes that broke Liquid templates and Jekyll in general - https://github.com/Shopify/liquid/issues/1625
https://github.com/jekyll/jekyll/issues/9094

So the workaround was to install Ruby 3.1.3 and switching my Rakefile to use the AWS CLI client instead of s3_website.

Since the Jekyll docs were still recommending to use s3_website I pushed a patch to change that recommendation

https://github.com/jekyll/jekyll/pull/9221

Back in June I tried to update my Jekyll blog. I did a bad job of tracking the Ruby version that was used with it. It was originally built in like 2013 with like Ruby 1.x series. In June I updated it and fought some dependency hell to get it to use Ruby 2.x and update Jekyll to 4.x. I built the site on MacOS but was never confident enough to actually push the update to the site.

Well, I went through the whole thing all over again tonight, updating to use Ruby 3.1

@nat @skyfaller This may not be the case now, but for a while the Inky was publishing a lot of work that PA Spotlight was doing. At one point I was subscribed to the Inky and also donating to PA Spotlight, but after a while the editorials of the Inky pissed me off enough where I stopped subscribing. I still donate to PA Spotlight.

@nedbat @sc68cal - yes, but in this context, a useful CI/CD for database migrations is one where you have tests that check certain things, and catch mistakes. A CI/CD pipeline that just posts a passive-aggressive message and forces someone to reply "i've read the docs" does not catch any real errors. It just acts as a speedbump.

@nedbat and if they keep doing the wrong thing after I warned them to stop, it's time to get management involved.

@nedbat writing a CI/CD pipeline that nags people to read and acknowledge documentation is far more work than me talking to someone and telling them to be more careful.

@nedbat if your team is not reading documentation about database migrations, that's a people problem not a CI/CD problem.

@paris OpenStack has a CI/CD system that I judge everything else by

@nedbat so you don't really want contributions. I mean if you're going to go to those lengths to make someone say "I know what I'm doing" just don't accept PRs.

@inkypitchbot too real