#random (2022-04)

Interesting, I’m using an M1 mac. Using Rosetta everything is working as expected.

Somehow I’m the one supporting the engineer, and I don’t even use a mac. So I had to discover that rosetta is a thing first.

Looks like most things are being installed ok now that she’s using rosetta. Still got some hoops to jump through though.

Fwiw, geodesic works on M1. So just get everything running in geodesic and then it’ll run everywhere™

I’m on M1 and the setup with roseatta that @Wédney Yuri mentioned is pretty painless. I use python, serverless framework and vscode. I think the most difficult part was npm with rosetta, but again, it was simply making sure to use rosetta during the install

We’re using asdf to install stuff, after installing rosetta most stuff there was working. The last thing we were fighting with yesterday was getting python installed via asdf, we’ll see how that goes.

I’m really hoping I don’t have to rewrite our local setup again. But if I do, I’ll definitely check out geodesic.

Geodesic would work with what you have today

just stick the asdf stuff into a container. done.

That could get weird. I use asdf to install k3d. So we’d be running k3d in a container which runs k8s in a container.

it actually works, since all you need to do is mount the docker sock to the container, and geodesic already does that

Huh, good point.

Got past the early issues, and now k3s is running and some containers are starting fine, but our applications use a custom go tool as part of their startup and that’s segfaulting in the container.

sigh… ya, this was the problem we had originally when trying to distribute tools for developers, that led us to decide to use a toolbox image so we could control for all variances

I told my boss we should just make everyone use linux. It didn’t fly.

Not that I thought it would… but it sure would make my life easier.

Necroing a little here, but on my most recent project we had the opposite happen. Every developer on the team either used Linux or Mac (also linux). We ended up getting a new developer that used windows and it took them a good day or so to get up and running. Company ended up putting a policy in place to keep development scripts as portable as possible… Also the day I learned that I am a complete noob with windows.

I haven’t used Windows regularly since about 2014. I’ve told my boss that if he lets someone use windows they’re on their own to get stuff working.

I am happy to see ARM getting its day in the sun. I’m far from a cpu arch guru, but the small amount I have experienced with ARM has been pleasant. The M1 is a great chip; just a matter adopting Darwin from what I’ve heard. I’ve only ran into a handful of software that didn’t have a solution for M1.

Could be wrong though, I’m not sure if the problem lies in the underlying ARM arch (which would be surprising, ARM is nothing new), or Darwin itself

Haha great stuff — the entire west coast is represented

I’m surprised to see Philly on their list. Philly is my home town, but I wouldn’t count it as a great beer spot.

Living in Boulder, CO feels like a privileged in regard to the beer world. I have a ton of killer breweries around me.

Yeah. I like that CA has a couple nods but honestly, the entire South Bay of Los Angeles was overlooked. We have several awesome breweries down here minutes from each other… https://discovertorrance.com/explore/indulge/breweries/

And if you’re into liquors this spot is another good one. its downtown so closer to LA Live, Convention Center, etc… https://ladistillery.com/

One more and I will stop… https://greenbardistillery.com/

also downtown

Haha my best friend is in LA so pre-pandemic I typically got there once a year. Those are all now saved as want to go in GMaps so I’ll be sure to check em out — Thanks for sharing!

Cincinnati is not a bad town for craft beer. There is quite a lot of beer history here too. I can’t directly compare it with Cleveland but Cincinnati is a good. These are the best of times for craft beer.

I’m thinking of going

I’m in Austin may join that.

Looks awesome, could have used that a couple years ago

Don’t have a use at the moment, but I’ll definitely add it to my “this might come in handy” list.

anyone remember using scponly to do this kinda thing? https://github.com/scponly/scponly Them were the days….

and rssh

We are using release drafter based on github tags https://github.com/release-drafter/release-drafter

And just implemented a slack command to create a new tag and release.

I just use a version file in the repo. Increment the version, write a changelog entry, as part of the pr. CI checks the version file and compares against the current tag, if newer version then it creates the release

Looking to automate this so that:

• People can’t forget to put in a CHANGELOG entry

• Changelog isn’t garbage

• Automated releases so we aren’t manually cutting/bumping version numbers.

the first can be done with a ci check on the pr. the second is extremely subjective. the third always requires human input anyway IMO (what determines which token to bump, major, minor, patch?)

https://github.com/semantic-release/semantic-release looks interesting but node

The release version is determined by the commits that go into the release

and how were those commits created?

not trying to be difficult. just haven’t seen anything that really addresses those requirements, at least not without introducing a bunch of other difficulties

by humans enforced standards via CI

conventional commits is a popular thing that there are actions to enforce… this can help use commits to generate readable changelogs… https://www.conventionalcommits.org/en/v1.0.0/

Right, https://github.com/semantic-release/semantic-release can use https://www.conventionalcommits.org/en/v1.0.0/

right, but that’s node. with conventional commits, github releases can generate a decent changelog automatically… i’ve used this action before, again just using a file to determine the version number, https://github.com/softprops/action-gh-release#-customizing

personally i don’t like conventional commits, but mostly because i have a hard enough time just unbreaking people’s git workflows as it is. the idea of having everyone on my team and driveby contributors understand rebasing and editing commit messages is overwhelming

Yeah, that is a concern

and yesh, not keen on a nodejs project but if it doesn’t throw up all over my repo and does what I want, can live with it.

Looks like semantic-release creates package.json and lock in the repo

lulz all your projects are node projects now

nope

release-drafter looks pretty nice also

ah ha, got that removed

Using semantic-release right now to publish GitHub release and generate changelogs, it does not create package.json files if not told to do so. There are ongoing efforts to rewrite it in go by some folks in here: https://github.com/go-semantic-release/semantic-release, not sure if it’s feature complete at the time.