| [06:24:18] | * farmBOT has joined #farmos |
| [08:27:52] | * farmBOT has quit (Ping timeout: 252 seconds) |
| [08:28:15] | * farmBOT has joined #farmos |
| [09:03:52] | <mstenta[m]> | I also sent out a newsletter to announce the blog: https://twitter.com/getFarmier/status/1587792223579561985 |
| [09:05:18] | <mstenta[m]> | We should add something about writing blog posts in https://github.com/farmOS/farmOS/blob/2.x/CONTRIBUTING.md |
| [11:18:50] | * heartburn has quit (Read error: Software caused connection abort) |
| [11:19:28] | * heartburn has joined #farmos |
| [12:49:05] | <mstenta[m]> | Hey all! Some other news... YouTube started offering "handles" for channels, so I reserved the @farmOSorg handle |
| [12:49:13] | <mstenta[m]> | (@farmOS wasn't available for some reason) |
| [12:49:29] | <mstenta[m]> | https://www.youtube.com/@farmOSorg |
| [12:50:25] | <mstenta[m]> | https://github.com/mstenta/farmOS-community-blog/pull/1 |
| [12:50:26] | <mstenta[m]> | I had to record a "farmOS in 5 Minutes" video for the upcoming PASA conference this morning, so I uploaded that to it (still unlisted at the moment), but also figured it might be a good test for embedding YouTube videos in blog posts! |
| [12:50:43] | <mstenta[m]> | What do you think symbioquine jgaehring paul121 ? |
| [12:51:29] | <mstenta[m]> | What's the best way to test how that displays? Do I need to run code locally? We don't have a way to preview in Netlify yet, huh? |
| [12:51:58] | <mstenta[m]> | All I did was copy and paste the "embed" code from YouTube... but not sure if that will require adjustment (or if we eventually want some kind of standardized embed template?) |
| [13:08:49] | <symbioquine[m]> | Once it's checked into any GitHub branch testing locally is trivial... |
| [13:11:16] | <symbioquine[m]> | https://github.com/farmOS/farmOS.org/blob/0f2d58643951ed0913884c0d24e7f3... |
| [13:12:01] | <symbioquine[m]> | Then run `npm run build && npm run serve` |
| [13:45:12] | <jgaehring[m]> | <mstenta[m]> "What's the best way to test..." <- I briefly mentioned this to this [here](https://github.com/farmOS/farmOS-community-blog/issues/5), but I think the best way would be to set up preview branches in the `farmOS/farmOS.org` repo that targets a specific branch on a source repo, maybe set up a `staging` repo or something for each for drafts, or what have you, like I did with the fork for that PR: |
| [13:45:12] | <jgaehring[m]> | https://github.com/farmOS/farmOS.org/blob/source/farmOS/source-repos.js#L7 |
| [13:47:10] | <jgaehring[m]> | could probably finesse the GH action to target PR's on source repo's and build from whatever fork or branch is being merged, but that would be the gist of it |
| [18:28:20] | <paul121[m]> | interesting. I wonder if we could kinda make our own "deploy preview" manually.... could we maybe have a GH action in farmOS-community-blog that clones farmOS/farmOS.org, changes the source repo branch to farmOS-community-blog@PR, runs webpack build, and saves it as an artifact viewable in the PR? |