IRC logs for #farmOS, 2022-01-31 (GMT)

2022-01-30
2022-02-01
TimeNickMessage
[20:52:50]<symbioquine[m]>Got it working with the alter hooks;
[20:52:56]<symbioquine[m]>ACTION uploaded an image: (62KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/XZbwYOcAYNt... >
[20:53:23]<symbioquine[m]>ACTION sent a php code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/868a686412...
[03:35:27]* matrixtrix[m] has quit (Ping timeout: 268 seconds)
[03:35:52]* matrixtrix[m] has joined #farmos
[04:26:16]* farmBOT has joined #farmos
[06:24:19]<mstenta[m]>symbioquine: huzzah! that's great!
[06:26:21]<mstenta[m]>i suppose the only disadvantage of the hooks is they would take precedence over the "entity form/view display" config. it's possible that someone may override those on their own instance, to customize the ordering/display of fields. these hooks would then apply changes *on top of* those overrides, i believe...
[06:27:02]<mstenta[m]>this is probably why i didn't go that route in farmOS core for the few taxonomy term fields we add - so that it didn't impede downstream customization
[06:28:20]<mstenta[m]>i think anyway...
[13:23:31]* ludwa6[m] has joined #farmos
[13:23:32]<ludwa6[m]>Hello room: been outta the loop since... Well, before v2.0 release! Now it is high time i guess to check into the possibility of migrating my instance. Are there others with a Farmier-hosted instance of v2.x in production, i wonder?
[13:23:47]<mstenta[m]>Hi ludwa6 ! 👋
[13:24:28]<mstenta[m]>Yes, in fact - all new instances created on Farmier are v2 now :-)
[13:24:40]<mstenta[m]>I'm almost ready to begin migrations of existing sites...
[13:25:19]<mstenta[m]>Couple of setbacks with children home from school and a blizzard 😅
[13:25:26]<ludwa6[m]>mstenta[m]: cool, @mstenta ; good timing!
[13:26:27]<ludwa6[m]>mstenta[m]: Yikes! the madness continues on both sides of the pond, alas.
[13:27:16]<ludwa6[m]>Blizzard sounds almost good to me -i would take any form of precip at this point, as we are facing catastrophic drought this summer.
[13:27:38]<ludwa6[m]>But of course grass is always greener on the other side of the fence, so... Sympathies!
[13:27:46]<mstenta[m]>Oh I'm sorry to hear! I wish we could send some your way
[13:27:53]<mstenta[m]>The grass is quite white here now
[13:27:59]<ludwa6[m]>:-)
[13:30:15]<ludwa6[m]>Anyway: i'm gonna get my @55 back in gear on the farmOS front. Besides all the madness, i've been too busy getting our new www.valedalama.net site online... And now we are creating a new farm shop on OpenFoodNetwork (thanks to you for turning me on to that one!)
[13:31:44]<ludwa6[m]>In fact -tho our OFN:PT group is hosted on a server in Spain right now- we are investigating possibility of hosting our own instance of OFN.
[13:32:24]<ludwa6[m]>Of course the idea of local server administration kinda gives me the willies... But it could be an idea whose time has come.
[13:38:36]<ludwa6[m]>Meanwhile, i have to ask (in view of some chatter a bit upstream in this channel about taxonomy): is taxonomy related to plant types, crops, etc. in a stable form now? I ask, because i need to pick up where i left off with paul121 about uploading our crop plans & harvest logs via API. Can we consider the data model in that area quite stable?
[13:40:29]<mstenta[m]>Oh awesome to hear you're using OFN!
[13:40:57]<mstenta[m]>Yes I would say the plant type stuff is not going to change any time soon
[13:42:03]<ludwa6[m]>mstenta[m]: Yeah -it seems to me like the closest thing to a standard in our field, to address the customer-facing stuff.
[13:43:42]<ludwa6[m]>mstenta[m]: Great; that should make it easy to reboot our data integration efforts.
[13:51:21]<paul121[m]>yep! farmOS 2 should be ready for your data ludwa6 , I think we just had some lingering questions about how to import some things... "conventions" about how you + your team expected data to show up so it can be reviewed, etc
[15:04:50]<ludwa6[m]><paul121[m]> "yep! farmOS 2 should be ready..." <- yes paul121 : in fact that's where i got sidetracked, waiting for some clarity to emerge about data conventions related to the RealFoodCampaign in which we are participating... And then while waiting on that, we got involved in the OFN project, which has it's own standards -still in a flux, but there is this prototype APi available at
[15:04:50]<ludwa6[m]>https://app.swaggerhub.com/apis/Open-Food-Network/Open-Food-Network-API/...
[15:07:21]<ludwa6[m]>... but that one came with a warning: subject to change, so don't build any production systems on it. Finally i am forced to conclude: it's not worth waiting on this stuff, we need to move ahead, because the opportunity cost of having no database in production is just too much.
[15:11:24]<paul121[m]>Cool. Trying to maintain some consistency with RFC makes sense. But I'm not surprised that it's too early to make decisions re: OFN :-)
[15:12:31]<paul121[m]>I imagine there will be more general differences between production and harvest/store data anyways - so maybe not best to think of it all the same? (really not sure tho)
[15:13:14]<paul121[m]>(obviously an organic flag could carry over... but.. idk.. not trying to get into the weeds with that :-))
[15:13:32]<ludwa6[m]>paul121[m]: You are right: i am conflating two issues between which there should be a layer of abstraction.
[15:15:24]<ludwa6[m]>I just had this naive idea that data about our crops-in-field would flow right through harvest to inventory in our food hub and ultimately customer orders... But that's kinda crazy, i guess, huh? <8-)...
[15:16:00]<mstenta[m]>`product` asset type! :-)
[15:16:29]<mstenta[m]>+ quick forms for managing the "transition" to product
[15:16:36]<mstenta[m]>s/+/plus/
[15:16:41]<ludwa6[m]>Oh, and (lest i forget): would harmonise with names of crops per RFC as well.
[15:17:13]<ludwa6[m]>Why can't we all just get along?
[15:17:15]<mstenta[m]>plus "metrics" to summarize product inventory/availability (maybe even projections?)
[15:17:35]<ludwa6[m]>Sure, that too.
[15:17:36]<mstenta[m]>plus OFN integration to "push" metrics data!
[15:17:47]<ludwa6[m]>Ooh, yeah!
[15:18:04]<mstenta[m]>that's the "point A to point B" summary in my mind
[15:19:37]<ludwa6[m]>Seriously tho: i am not quite seeing a clear point A to point B. How we can ever get to real transparency & traceability in our food system is rather beyond me.
[15:19:59]<mstenta[m]>> plus quick forms for managing the "transition" to product
[15:20:00]<mstenta[m]>maybe just a general-purpose "Harvest quick form" that has a checkbox "do you want to create/add to product assets from this harvest?" which creates/increments product inventory alongside the creation of harvest logs
[15:20:53]<ludwa6[m]>Am starting to feel like the butt of the old joke: How many M$ft engineers does it take to change a lightbulb? A: none - they just declared darkness to be the new standard.
[15:21:06]<mstenta[m]>haha
[15:21:57]<mstenta[m]>traceability isn't too hard if you have the data... it's mostly a data entry problem i think
[15:22:24]<paul121[m]>> <@mstenta:matrix.org> > plus quick forms for managing the "transition" to product
[15:22:24]<paul121[m]>>
[15:22:24]<paul121[m]>> maybe just a general-purpose "Harvest quick form" that has a checkbox "do you want to create/add to product assets from this harvest?" which creates/increments product inventory alongside the creation of harvest logs
[15:22:24]<paul121[m]>ideas on doing this if ludwa6 is importing harvest data via csv?
[15:22:54]<mstenta[m]>you could create/increment product assets via API too (once there is a `product` asset type)
[15:23:04]<paul121[m]>right
[15:23:43]<ludwa6[m]>mstenta[m]: well, yeah: entry & REentry, ad infinitum -which multiples the risk of redundant conflicting data at every turn.
[15:24:31]<ludwa6[m]>This CSV import path is sure to create such problems. API entry (with data integrity constraints) must be the way to go.
[15:26:21]<ludwa6[m]>Guess it's a moot point, since CSV import to v2 is not available -not now, and not any time soon, right?
[15:27:18]<paul121[m]>yea - by CSV import I really mean the API import script
[15:27:38]<ludwa6[m]>paul121[m]: ah, ok
[15:31:20]<ludwa6[m]>oops: 8:30pm local: gotta go, it's film nite down here on the farm. TTY again soon ciao for now.
[16:24:26]<MarcosCarballal[>Hey all, SFI dev is reproducing this issue across 3 different Windows Host Machine.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/86d06ec013...)
[16:24:29]<MarcosCarballal[>ACTION uploaded an image: (81KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/bgDmMiNpbeO... >
[16:25:48]<mstenta[m]>You are running Docker on Windows?
[16:26:10]<MarcosCarballal[>Yes, for the purpose of a local development environment
[16:26:57]<mstenta[m]>I think someone else ran into this before... on Windows... might be on the forum let me check...
[16:27:19]<mstenta[m]>IIRC it has to do with file permissions when you bind-mount Windows directory into a linux container
[16:28:17]<mstenta[m]>the example `docker-compose.yml` file you pasted above bind-mounts the entire farmOS codebase as a volume (creating a local `www` directory and mounting that into the container as `/opt/drupal` - which is where the Docker container looks for the farmOS codebase)
[16:28:42]<mstenta[m]>I bet if you remove these lines it will work:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/76f4f64a35...)
[16:29:00]<MarcosCarballal[>Let's give it a shot.
[16:29:02]<mstenta[m]>however... that's necessary for persisting everything :-)
[16:29:31]<mstenta[m]>so it's not a solution - just something to test which will confirm that it's an issue with the mounted volume permissions
[16:29:33]<MarcosCarballal[>Yeah, not a permanent solution
[16:31:38]<mstenta[m]>TBH the docker environment instructions are only tested on linux, so your mileage may vary on Windows :-)
[16:32:03]<MarcosCarballal[>Yup, it spun to life just fine. Maybe I just need to change the Windows folder permissions.
[16:32:05]<mstenta[m]>i'm still looking for the past conversation with the person who had a similar issue...
[16:33:46]<mstenta[m]>OH!
[16:33:53]<mstenta[m]>Try this...
[16:34:18]<mstenta[m]>instead of `farmos/farmos:2.x-dev`, use `farmos/farmos:2.x`
[16:34:38]<mstenta[m]>(with the bind-mount enabled)
[16:34:54]<MarcosCarballal[>Yup, trying it now.
[16:36:05]<mstenta[m]>You aren't going to be doing any core farmOS development, so I don't think you'll need the `2.x-dev` image...
[17:13:14]<MarcosCarballal[>Switching to `2.x` on its own didn't solve the issue. However, installing WSL (Ubuntu 20.04) and hosting the `db` and `www` folders in the "Linux part" of the file system seemed to do the trick. Must be something with the reading/writing files that Windows does not like. I'm happy to type up a quick explanation of this approach if it would be helpful to other trying to develop on Windows.
[17:13:50]<mstenta[m]>oh excellent! good sleuthing!
[17:15:26]<mstenta[m]>Oh just found this in the forum (searching for "WSL): https://farmos.discourse.group/t/developing-in-windows-with-docker-and-w...
[17:15:28]<mstenta[m]>Not sure if you need that... if it's working then maybe not!
[17:16:28]<mstenta[m]>Feel free to add your findings to that thread if you want!
[17:16:48]<MarcosCarballal[>Will do!