| [09:54:48] | <mstenta[m]> | symbioquine: I just tested posting to the microblog via the farmOS repo (using the `ssh-key` w/ deploy key) and it worked! |
| [09:55:01] | <mstenta[m]> | https://github.com/farmOS/farmOS/actions/runs/3508490104 |
| [09:55:04] | <mstenta[m]> | https://github.com/farmOS/farmOS-microblog/actions/runs/3508491082 |
| [09:55:27] | <mstenta[m]> | https://fosstodon.org/@farmOS/109376698668985313 |
| [09:55:57] | <mstenta[m]> | So I'm confident that the weekly dev call announcement on Thursday will work (and the future release announcements from the farmOS repo) 👍️ |
| [09:56:25] | <mstenta[m]> | But then it made me realize... Thursday is Thanksgiving! 😄🦃 |
| [09:57:38] | <mstenta[m]> | I probably won't be able to make the call myself - maybe others will? I don't think there's any harm in letting the tweet go out... but it just made me think about whether or not we need some mechanisms to modify the auto-announcement behavior from time to time |
| [09:58:02] | <mstenta[m]> | I guess we can just wait and see if it comes up... |
| [09:58:41] | <mstenta[m]> | One idea I had was to add a text file to the repo with "ignore dates" or something... so the announce workflow could check it and if the current date matches an ignore date it cancels the job |
| [09:59:02] | <mstenta[m]> | (Might also be useful to do something similar for "scheduled posts" in the future!) |
| [10:00:13] | <mstenta[m]> | > it just made me think about whether or not we need some mechanisms to modify the auto-announcement behavior from time to time |
| [10:00:13] | <mstenta[m]> | a simple solution for last-minute changes might be to just disable the action temporarily: https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-... |
| [11:26:34] | <symbioquine[m]> | <mstenta[m]> "I probably won't be able to make..." <- One short-term option might be manually replying to the tweet/toot to indicate that the USA based folks probably won't make it due to the holiday. |
| [11:26:56] | <symbioquine[m]> | > <@mstenta:matrix.org> > it just made me think about whether or not we need some mechanisms to modify the auto-announcement behavior from time to time |
| [11:26:56] | <symbioquine[m]> | > |
| [11:26:56] | <symbioquine[m]> | > a simple solution for last-minute changes might be to just disable the action temporarily: https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-... |
| [11:26:56] | <symbioquine[m]> | Or that |
| [11:56:42] | <mstenta[m]> | Farmer Ed: Question about how you're building https://hub.docker.com/r/farmered/farmos... |
| [11:57:33] | <mstenta[m]> | I am testing out `docker buildx` in a branch here: https://github.com/farmOS/farmOS/compare/2.x...mstenta:farmOS:2.x-buildx |
| [11:57:58] | <mstenta[m]> | Currently it is failing on the first `RUN` step in our `Dockerfile` though: https://github.com/mstenta/farmOS/actions/runs/3508900680/jobs/5877631877 |
| [11:58:31] | <mstenta[m]> | ERROR: failed to solve: executor failed running [/bin/sh -c echo "ServerName localhost" >> /etc/apache2/apache2.conf]: exit code: 1 |
| [11:59:18] | <mstenta[m]> | Curious if you ran into this and had to do anything... or if (more likely) I need to do more in my setup than simply add `buildx` and `--platform` to my commands :-) |
| [12:01:04] | <mstenta[m]> | > I am testing out `docker buildx` in a branch here: https://github.com/farmOS/farmOS/compare/2.x...mstenta:farmOS:2.x-buildx |
| [12:01:04] | <mstenta[m]> | (oops that diff also show the commit from https://github.com/farmOS/farmOS/pull/599 - ignore that) |
| [12:03:25] | <mstenta[m]> | ah i might need https://github.com/docker/setup-buildx-action |
| [12:09:19] | <mstenta[m]> | oh might have fix it by simply adding `docker/setup-qemu-action@v2` |
| [12:52:26] | <mstenta[m]> | seems to have worked! the only thing left to test is pushing to Docker Hub (and pulling to a raspberry pi to confirm it works) |
| [12:54:03] | <mstenta[m]> | wow - takes a LOT longer to build the arm64 images :-/ |
| [12:54:44] | <mstenta[m]> | might be worth splitting those out to a separate job that runs in parallel, so it doesn't block tests/sniffs from running |
| [12:59:37] | <FarmerEd[m]> | I guess the ARM64 processor is not one of the new Mac ones. |
| [16:00:27] | <mstenta[m]> | I opened this new issue and documented how far I got - probably won't have time to work on this again soon, so if anyone else is interested feel free to pick up where I left off! https://www.drupal.org/project/farm/issues/3322762 |
| [17:25:47] | <mstenta[m]> | paul121: I think you're working on the same thing I am 😆 |
| [17:26:25] | <mstenta[m]> | https://github.com/mstenta/farmOS-microblog/actions/workflows/workflow_d... |
| [17:26:55] | <mstenta[m]> | Looks like you are a step ahead of me though |
| [17:27:03] | <paul121[m]> | hahah |
| [17:28:43] | <mstenta[m]> | Oh wait not quite |
| [17:28:57] | <paul121[m]> | I didn't see those action runs! |
| [17:29:22] | <mstenta[m]> | Ah nevermind, misread PR for a second |
| [17:29:38] | <mstenta[m]> | Yea! Cool! You definitely are ahead of where I was, so I'll check out yours |
| [17:29:52] | <mstenta[m]> | I was starting to just get some validation via bash commands, so maybe we can work that in afterwards |
| [17:30:27] | <mstenta[m]> | (eg: make sure message is less than 280 chars, and doesn't include double-quotes (my `git commit -m` uses double quotes) |
| [17:30:34] | <paul121[m]> | yeaaa making sure that messages aren't too long, was thinking that could be next :-) |
| [17:30:43] | <paul121[m]> | reason to consolidate all of this to one place :-) |
| [17:32:54] | <mstenta[m]> | Gonna need a clever commit message 😄 |
| [17:33:49] | <mstenta[m]> | (or maaaaybe... I wonder if a merge commit message would be a good way to get code PRs merged while maintaining their own commit messages) |
| [17:35:56] | <paul121[m]> | that might work!!! |