IRC logs for #farmOS, 2022-11-15 (GMT)

2022-11-14
2022-11-16
TimeNickMessage
[22:26:01]<symbioquine[m]>Does `/api/asset/animal/resource/relationships/parent/related/schema` work for folks? Mine fails...
[22:26:13]<symbioquine[m]>ACTION uploaded an image: (349KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/kpXVUdSIoBX... >
[22:28:58]<symbioquine[m]>My guess right now is that it's caused by relationships that aren't constrained to a particular asset bundle.
[22:29:41]<symbioquine[m]>It's not blocking me, just curious if it's a known issue. I didn't see one in a quick search of the Drupal core issue queue.
[23:31:41]<threewordchant>first rough draft of "deploy farmos using co-op cloud" blog post https://pad.autonomic.zone/s/uE32aFOcb#
[23:32:04]<threewordchant>i plan to add some screenshots, still mulling a video. in the meantime any feedback welcome, particularly on:
[23:32:04]<threewordchant>- tone
[23:32:24]<threewordchant> * i plan to add some screenshots, still mulling a video. in the meantime any feedback welcome, particularly on:
[23:32:24]<threewordchant>- tone, length, how much background info to give
[23:32:24]<threewordchant>- level of tech knowledge to assume
[23:32:42]<threewordchant> * i plan to add some screenshots, still mulling a video. in the meantime any feedback welcome, particularly on:
[23:32:42]<threewordchant>- tone, length, how much background info to give
[23:32:42]<threewordchant>- level of tech knowledge to assume
[01:46:18]* farmBOT has joined #farmos
[06:29:58]<mstenta[m]>That's great 3wc ~ they/them!!
[06:31:56]<mstenta[m]>Gave me a better understanding too! 😄
[06:31:57]<mstenta[m]>Some questions/followup thoughts specific to farmOS...
[06:32:01]<mstenta[m]>Is there a way to control the version (Docker image tag)?
[06:33:41]<mstenta[m]>Updates from one version to another require running update.php and cache rebuild, we recommend doing that via Drush but it can usually be done via UI too. So generally speaking version upgrades need to be done intentionally.
[06:35:31]<mstenta[m]>> You can also use abra app downgrade farmos.demo.coopcloud.tech to return to an earlier version in case of problems
[06:35:31]<mstenta[m]>Does this also handle rolling back the database? Drupal doesnt do that automatically, so if this just downgrades the Docker image version, but database updates have occurred with the upgrade, then downgrading code could leave you in a broken state
[06:39:16]<mstenta[m]>> run abra app upgrade farmos.demo.coopcloud.tech to upgrade to the latest version
[06:39:16]<mstenta[m]>I assume this uses the "latest" tag? That should work, but as described above we recommend specifying a specific version so it is intentional and you know which version you were on previously so you cab roll back and restore backup if necessary
[06:39:17]<mstenta[m]>> Your database settings will be:
[06:39:17]<mstenta[m]>Looks like these are using the default dev environment values (all "farm"). Production instance should customize these for security. Is that possible?
[06:40:09]<mstenta[m]>Other than those minor bits this looks really good!
[06:41:16]<mstenta[m]>Not sure if you're planning on posting this to your own blog, but would you be interested in cross-posting it on the farmOS.org blog too? You can set the canonical tag to point to yours
[08:49:18]<threewordchant>awesome thoughts, thank you mstenta!
[08:50:04]<threewordchant><mstenta[m]> "Is there a way to control the..." <- yes, co-op cloud "recipe" versions are usually pinned to a docker tag. FarmOS is currenty using 2.x but I'll switch it to a specific one
[08:54:39]<threewordchant><mstenta[m]> "Updates from one version to..." <- oh good call, I'll add the commands to do both to the post
[08:55:44]<threewordchant>> <@mstenta:matrix.org> > You can also use abra app downgrade farmos.demo.coopcloud.tech to return to an earlier version in case of problems
[08:55:44]<threewordchant>>
[08:55:44]<threewordchant>> Does this also handle rolling back the database? Drupal doesnt do that automatically, so if this just downgrades the Docker image version, but database updates have occurred with the upgrade, then downgrading code could leave you in a broken state
[08:55:44]<threewordchant>no, Co-op Cloud doesn't currently automatically roll back the DB - I'll edit the post to recommend making a DB backup, and saying how to restore it after a downgrade.
[08:56:55]<threewordchant>> <@mstenta:matrix.org> > run abra app upgrade farmos.demo.coopcloud.tech to upgrade to the latest version
[08:56:55]<threewordchant>>
[08:56:55]<threewordchant>> I assume this uses the "latest" tag? That should work, but as described above we recommend specifying a specific version so it is intentional and you know which version you were on previously so you cab roll back and restore backup if necessary
[08:56:55]<threewordchant>there's a guided semi-automatic process to pick up new image tags for a new numbered version, which is driven by `abra recipe upgrade farmos` - but this is done centrally by the "recipe maintainer" to make the new version available to all deployments
[08:57:49]<threewordchant>> <@mstenta:matrix.org> > Your database settings will be:
[08:57:49]<threewordchant>>
[08:57:49]<threewordchant>> Looks like these are using the default dev environment values (all "farm"). Production instance should customize these for security. Is that possible?
[08:57:49]<threewordchant>good point. I sometimes get a bit lazy about db credentials because the database isn't remote-accessible. but there is a way to have `abra` auto-generate a password and store it as a Docker secret.
[08:58:36]<threewordchant>do you know if there's a way to prefill the info in the web installer? otherwise i worry it could add a slightly confusing step to add that. but maybe it's still better than using a preset insecure password 🤔
[08:58:57]<threewordchant><mstenta[m]> "Not sure if you're planning on..." <- i'm easy either way! had sort of been imagining posting it primarily on farmos.org blog if y'all are willing
[09:25:41]<mstenta[m]>> do you know if there's a way to prefill the info in the web installer? otherwise i worry it could add a slightly confusing step to add that. but maybe it's still better than using a preset insecure password 🤔
[09:25:41]<mstenta[m]>Hmm well... it has to be set up in the PostgreSQL container first, which you then reference from the Drupal/farmOS installer...
[09:26:28]<mstenta[m]>But after that, there are two ways to install Drupal/farmOS: 1) via the web UI, 2) via `drush site-install`
[09:27:18]<mstenta[m]>The db credentials can be passed as arguments to that
[09:27:19]<mstenta[m]>https://www.drush.org/latest/commands/site_install/
[09:28:08]<mstenta[m]>If you use `drush site-install` you also have to specify the installation profile (`farm`) otherwise it will install a standard drupal site
[09:28:33]<mstenta[m]>You can also tell it to enable the default farmOS modules with `farm.modules="default"`
[09:29:18]<mstenta[m]>Example: https://github.com/farmOS/farmOS/blob/f939c8074450b179b83cdd98ee121f4a51...
[09:29:27]<mstenta[m]>(That line installs "all" modules... just change `all` to `default`)
[09:44:03]<threewordchant>nice, thanks! I'll add that to the recipe too, love a good autoinstall
[09:45:02]<threewordchant>> <@mstenta:matrix.org> > do you know if there's a way to prefill the info in the web installer? otherwise i worry it could add a slightly confusing step to add that. but maybe it's still better than using a preset insecure password 🤔
[09:45:02]<threewordchant>>
[09:45:02]<threewordchant>> Hmm well... it has to be set up in the PostgreSQL container first, which you then reference from the Drupal/farmOS installer...
[09:45:02]<threewordchant>and yes, the postgres image already supports docker secrets so that part's easy
[09:50:36]<mstenta[m]>awesome!
[11:44:48]<mstenta[m]>> Does `/api/asset/animal/resource/relationships/parent/related/schema` work for folks? Mine fails...
[11:44:49]<mstenta[m]>fails on test.farmos.dev too :-(
[11:44:54]<mstenta[m]>symbioquine^
[11:48:59]<mstenta[m]>I imagine it would be an issue with the `json_schema` module, if anything
[11:49:23]<mstenta[m]>Drupal core doesn't provide schema
[11:49:40]<mstenta[m]>Sorry I mean `jsonapi_schema`
[11:49:41]<mstenta[m]>https://www.drupal.org/project/jsonapi_schema
[11:50:29]<mstenta[m]>Is this it? https://www.drupal.org/project/jsonapi_schema/issues/3189930
[11:50:43]<mstenta[m]>Oh I opened that HA
[11:50:58]<mstenta[m]>😂
[11:51:24]<mstenta[m]>AND uploaded a patch
[11:51:36]<mstenta[m]>https://gifimage.net/wp-content/uploads/2017/11/i-have-no-memory-of-this...
[11:51:42]<symbioquine[m]>Cool, I'll have to take a look in a little while... :)
[11:52:18]<mstenta[m]>Oh even better... YOU opened the original issue symbioquine https://www.drupal.org/project/farm/issues/3189918
[11:52:21]<mstenta[m]>lol
[11:57:42]<paul121[m]>I thought that seemed familiar.... 🤣
[13:29:17]* farmBOT has joined #farmos
[14:38:21]<paul121[m]>I'm eager for a new farmos-map release.... what do ya think mstenta symbioquine ??
[14:41:55]<paul121[m]>also curious if the next release should be 2.1 or 2.0.9... I kinda lean towards 2.1 and doing more minor releases going forward. Going off memory it seems we wouldn't have had many true "patch" releases in the past, I think of this as a release with only bug fixes?
[14:41:56]<paul121[m]>But overall I don't have a strong opinion on this, mostly just want a new release :D
[15:06:43]<mstenta[m]>yea 2.1 sounds good to me!
[15:06:48]<mstenta[m]>if symbioquine is ok with it :-)
[15:07:10]<mstenta[m]>> But overall I don't have a strong opinion on this, mostly just want a new release :D
[15:07:10]<mstenta[m]>same :-)
[15:07:23]<mstenta[m]>i'm hoping to package a new release of farmOS soooon (this week or next)... so let's get a new release included either way
[15:30:02]<symbioquine[m]><mstenta[m]> "if symbioquine is ok with it :-)" <- I don't feel strongly about it. Go for whatever feels good :)
[16:38:15]<paul121[m]>hmm well I tagged v2.1.0: https://github.com/farmOS/farmOS-map/releases/tag/v2.1.0
[16:38:15]<paul121[m]>but it didn't trigger an action to create the release 🤔
[16:43:16]<mstenta[m]>Huh
[16:43:39]<mstenta[m]>Did Elon Musk buy GitHub too?
[16:44:06]<symbioquine[m]>hah
[16:44:06]<symbioquine[m]>Should just be the steps here: https://farmos.discourse.group/t/2-x-release-procedure/1070/4
[16:44:33]<symbioquine[m]>From what I can see it looks like you've done it right.
[16:45:02]<paul121[m]>thanks, I just came across the steps... I didn't do an `--atomic` push though?
[16:45:40]<paul121[m]>* push though. Maybe that is the issue?
[16:46:01]<mstenta[m]>Hmm I don't think so
[16:48:12]<symbioquine[m]>Maybe the GH action just hasn't gotten run yet?
[16:48:16]<mstenta[m]>What if you try deleting the tag and pushing again?
[16:48:31]<mstenta[m]>I would expect to see the action queued at least
[16:49:14]<paul121[m]>How do I delete the tag?
[16:49:21]<symbioquine[m]>Yeah, it's interesting that one of the workflows did run: https://github.com/farmOS/farmOS-map/actions/runs/3474192340
[16:49:26]<mstenta[m]>https://twitter.com/github_st_test/status/1592608944392114176
[16:49:59]<mstenta[m]>I think `git push origin :[tag]` will delete the tag from origin, then you can just `git push origin [tag]` again
[16:50:25]<symbioquine[m]>mstenta[m]: Weird, there status page doesn't show anything: https://www.githubstatus.com/
[16:50:32]<mstenta[m]>yea hmm
[16:50:49]<paul121[m]>okay let me try deleting
[16:51:36]<paul121[m]>seemed to work!
[16:51:38]<mstenta[m]>oh there we go
[16:51:40]<mstenta[m]>huh weird
[16:52:05]<mstenta[m]>¯_(ツ)_/¯
[16:52:07]<symbioquine[m]>Yay
[16:52:15]<symbioquine[m]>ACTION uploaded an image: (13KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/tuPLudhMTqg... >
[16:52:19]<mstenta[m]> * ¯\_(ツ)_/¯
[16:53:10]<paul121[m]>🎉 https://github.com/farmOS/farmOS-map/releases/tag/v2.1.0
[16:53:32]<mstenta[m]>Sometimes I worry that I'm basing too much of my life on github actions 😬
[16:53:41]<mstenta[m]>Could rebuild on GitLab or something if we had to... but at this point that would be non-trivial
[16:54:04]<paul121[m]>something something don't rely on webhooks 🤣
[16:54:16]<mstenta[m]>lol