| [04:52:03] | * med65[m] has quit (Ping timeout: 248 seconds) |
| [05:13:13] | * med65[m] has joined #farmos |
| [07:34:03] | * cpm has quit (Quit: Leaving) |
| [10:01:55] | <frakman1[m]> | Is there a sample/demo farm that is pre-populated that can be browsed and examined to better understand how things work? |
| [10:01:56] | <frakman1[m]> | I thought that under webpage's Community->Farms that those farms would indeed be community farms that users can look at but instead they are just lists of farms that use FarmOS. |
| [10:04:42] | <mstenta[m]> | not currently no :-( |
| [10:04:45] | <mstenta[m]> | but we have been discussing this |
| [10:04:47] | <mstenta[m]> | https://farmos.discourse.group/t/example-data-for-farmos/86 |
| [10:04:53] | <mstenta[m]> | https://farmos.discourse.group/t/use-tugboat-for-development-previews-an... |
| [10:05:38] | <mstenta[m]> | if you're interested in helping we would welcome it! |
| [10:07:06] | <frakman1[m]> | Thanks. From the first link, I see " try starting with the Quick Forms" |
| [10:07:06] | <frakman1[m]> | Where do I find this? Is this from within my farmos instance? |
| [10:07:42] | <mstenta[m]> | oh yea that's a good idea... whoever suggested that is smart ;-) |
| [10:07:59] | <mstenta[m]> | yes! are you self-hosting? or on farmier? |
| [10:08:10] | <mstenta[m]> | quick forms will appear under the "Quick" tab on the dashboard |
| [10:08:23] | <mstenta[m]> | * quick forms will appear under the "Quick forms" tab on the dashboard |
| [10:08:29] | <frakman1[m]> | FYI, I'm just starting with plantings and breaking areas into sub areas and it is a giant pain to rename them once it's already been created. It won't let you rename a top level area because of all the sub level beds underneath it. So I have to delete each one manually which is point and click hell. |
| [10:08:32] | <mstenta[m]> | you will need to first enable the ones you want |
| [10:08:55] | <mstenta[m]> | Renaming areas doesn't require changing children |
| [10:08:57] | <mstenta[m]> | Deleting them does |
| [10:08:59] | <mstenta[m]> | Is that what you mean? |
| [10:09:15] | <mstenta[m]> | FYI you can delete areas in bulk from the Areas menu item |
| [10:12:06] | <frakman1[m]> | I'm self-hosting. |
| [10:12:07] | <frakman1[m]> | I don't see a delete in bulk Areas menu item. When I click areas, I just see a map and a Hierarchy view on the right of the map |
| [10:12:12] | <frakman1[m]> | * I'm self-hosting. |
| [10:12:12] | <frakman1[m]> | I don't see a delete in bulk Areas menu item. When I click Areas, I just see a map and a Hierarchy view on the right of the map |
| [10:13:37] | <mstenta[m]> | click one of the checkboxes next to an area name in the hierarchy, and you should see a "Delete" button appear at the bottom |
| [10:13:54] | <mstenta[m]> | did you use the Bed Generator to create child areas? |
| [10:15:27] | <frakman1[m]> | Yes, I used Bed Generator. For sub-sub beds (in making a matrix for example) It defaults the numbering from bottom to top. Is it possible to make it count from top to bottom? i.e. bed 1 is the cell at top of column instead of the bottom? |
| [10:16:02] | <mstenta[m]> | Yes! I think that's in the docs (albeit a bit hidden)... on sec... |
| [10:16:53] | <mstenta[m]> | Oh maybe not in the docs... maybe in the UI itself... |
| [10:16:55] | <mstenta[m]> | > Areas will be numbered automatically in the direction of the orientation. For example: an orientation of 90 will number the areas from west to east, while an orientation of 270 will number the areas from east to west. Note that 0 and 360 are considered equivalent. |
| [10:17:01] | <frakman1[m]> | But I can't delete in bulk because of all the sub beds. That's the issue. Can't I force a delete? |
| [10:17:42] | <mstenta[m]> | Sorry - that's just the limitation it has right now |
| [10:18:10] | <mstenta[m]> | you can delete all the child areas, then all the parent areas |
| [10:18:25] | <mstenta[m]> | so still a lot of clicking involved... but less than deleting each separately |
| [10:19:24] | <mstenta[m]> | farmOS has "constraints" to prevent deleting any records that are referenced by another record - so that's why parent areas can't be deleted until their children are |
| [10:19:38] | <mstenta[m]> | and if you have any records associating the areas, it will also prevent deletion |
| [10:19:51] | <mstenta[m]> | * and if you have any logs associated with areas, it will also prevent deletion |
| [10:24:36] | <frakman1[m]> | "but less than deleting each separately". But that is deleting each one separately. |
| [10:24:36] | <frakman1[m]> | I have 5 columns, each with 13 rows. To delete them, I have to manually delete each of the 13*5 areas manually with all the confirms that go along with it. This is for a bed I just created with no attachments associated with the. |
| [10:24:48] | <frakman1[m]> | * "but less than deleting each separately". But that is deleting each one separately. |
| [10:24:48] | <frakman1[m]> | I have 5 columns, each with 13 rows. To delete them, I have to manually delete each of the 13*5 areas manually with all the confirms that go along with it. This is for a bed I just created with no attachments associated with them. |
| [10:25:31] | <mstenta[m]> | are you using the bulk delete on the child areas? or clicking each, then Edit, then delete, then confirm? |
| [10:28:53] | <mstenta[m]> | i agree it's tedious... just want to make sure you're doing the "less tedious" option :-) |
| [10:29:40] | <frakman1[m]> | All because I didn't choose the right name for the top level row so now all my cells have names like: zzz bed x bed y |
| [10:29:40] | <frakman1[m]> | Then didn't choose the right angle so the numbering is backwards so have to do it all over again. |
| [10:29:40] | <frakman1[m]> | OK, I see what you mean now. The "Delete" button on the Hierarchy page is what you are calling "bulk delete" and doing it there is faster than Edit->delte->confirm. |
| [10:29:56] | <frakman1[m]> | Thanks, I'll do the "less tedious" option now. haha |
| [10:30:21] | <mstenta[m]> | Cool! Yea the bed generator can be a bit of a "gotcha" in that way... and you end up needing to clean things up |
| [10:30:23] | <frakman1[m]> | I wish there was a way to reverse the numbering after it's been already done. |
| [10:30:26] | <mstenta[m]> | You're not the first to have this frustration |
| [10:30:48] | <mstenta[m]> | Yea that would be helpful - a bit tricky to implement that |
| [10:31:11] | <mstenta[m]> | I think ultimately what we need is for the bed generator itself to show the numbers in the preview |
| [10:31:16] | <mstenta[m]> | because once you go from "preview" to "create areas" then it's tricky to change |
| [10:31:22] | <mstenta[m]> | (I have to get on a call... brb) |
| [10:31:38] | <frakman1[m]> | Understood. I don't even know how to do it manually now because if I rename 13 to 1, it will conflict with the existing 1 so I have to call it something like 1.tmp etc. |
| [10:31:47] | <mstenta[m]> | Oof yea good point |
| [11:21:35] | * svenn has quit (Ping timeout: 258 seconds) |
| [11:24:43] | * svenn has joined #farmos |
| [11:55:09] | <frakman1[m]> | Another idea for bed generator, is to have a widget you can drag to change angle and show the preview lines in real-time. For plots that aren't perfectly perpendicular, it takes a lot of trial and error to find the right angle for the lines to be parallel to the area boundary. Then when you find it, and the numbers are backwards, you have to find the other angle that reverses it. |
| [11:56:28] | <symbioquine[m]> | That's what the snapping grid was originally designed to accommodate... https://farmos.org/guide/areas/#use-the-snapping-grid |
| [11:57:47] | <symbioquine[m]> | I'm also working on a simplified drawing interaction that should allow some similar cases even on mobile. |
| [12:01:49] | <symbioquine[m]> | Obviously, there's still a fair bit of manual work involved since there isn't currently a "multi-area drawing workflow" that allows drawing many areas on the same map instance and page load, but in theory one could make an area tool similar to this planting tool prototype demo: |
| [12:01:58] | <symbioquine[m]> | ACTION uploaded an image: (648KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/PkcSioiNpsBfOViT... > |
| [12:16:49] | <symbioquine[m]> | You could also potentially use my WFS module for farmOS to draw areas from qgis; https://github.com/symbioquine/farmOS_wfs/tree/7.x-1.x |
| [12:24:05] | <symbioquine[m]> | This video used an older implementation, but the user-facing experience would be pretty similar; |
| [12:24:05] | <symbioquine[m]> | https://www.youtube.com/watch?v=avwWeRJQBpY |
| [12:25:59] | <symbioquine[m]> | Start at [1:01](https://youtu.be/avwWeRJQBpY?t=61) to skip to the fun part :) |
| [12:53:21] | <paul121[m]> | symbioquine: think you could give us a general overview of QGIS one of these days? Clearly its a powerful tool for these sorts of things... I just haven't gotten past the hurdle of knowing what the buttons do and what buttons to look for |
| [12:53:35] | <paul121[m]> | a combo QGIS + WFS workshop would be SO COOL :-) |
| [12:55:12] | <symbioquine[m]> | Yeah, the learning curve for QGIS can be a bit steep. |
| [12:55:52] | <mstenta[m]> | > That's what the snapping grid was originally designed to accommodate... https://farmos.org/guide/areas/#use-the-snapping-grid |
| [12:55:53] | <mstenta[m]> | Gah! I totally forgot to suggest this lol - thanks symbioquine :-) |
| [12:56:40] | <mstenta[m]> | symbioquine: on a related note... the "Bed Generator" module is one of hte things on our list for farmOS 2.x pre-beta |
| [12:57:08] | <mstenta[m]> | And I'm wondering: can we just make it into a farmOS-map behavior of some kind, perhaps as a step towards a more complete farm mapping tool |
| [12:57:20] | <symbioquine[m]> | My feeling is that the snapping grid plus a "multi-area drawing workflow" could potentially be a better replacement for the "bed generator" concept... |
| [12:58:07] | <symbioquine[m]> | The main challenge is that it gets a bit trickier to generalize it for any asset and the area distinction goes away in 2.x |
| [12:58:50] | <mstenta[m]> | True... but for a first pass it could just be for "Land" assets (perhaps with a dropdown for "Land type") |
| [12:59:04] | <symbioquine[m]> | Makes sense |
| [12:59:15] | <mstenta[m]> | I wonder if you'd have any interest in some sponsored development work? :-) |
| [13:01:42] | <symbioquine[m]> | Maybe... I'm hoping to wrap up this touch drawing tool in the next couple weeks and I've got to time share between that sort of stuff and planting/seed-bank work :) |
| [13:01:56] | <mstenta[m]> | Oh right! I saw your agenda item! |
| [13:02:09] | <mstenta[m]> | Well if you're interested, feel free to ping me privately - happy to chat! |
| [13:03:41] | <mstenta[m]> | It's on our list of features that need to be ported to 2.x, but not super high priority, so timing is somewhat flexible... |
| [13:03:58] | <symbioquine[m]> | I'll share a sneak peek of the touch drawing concept... I'm super excited about it; |
| [13:04:06] | <mstenta[m]> | Cool! Can't wait! |
| [13:04:07] | <symbioquine[m]> | ACTION uploaded an image: (343KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/DiOcJxRdSTmXAmVv... > |
| [13:04:34] | <mstenta[m]> | 🤯 |
| [13:08:32] | <symbioquine[m]> | The idea is to provide handles/inputs to tweak the size/offsets/etc of the shape and explicit "save"/"cancel" buttons. |
| [13:09:07] | <mstenta[m]> | oh man that's great |
| [13:10:02] | <symbioquine[m]> | I haven't figured out how this "mode" gets enabled yet... |
| [13:10:11] | <mstenta[m]> | so is this a multi-area editor? does "Save" save the actual area record itself? |
| [13:10:27] | <mstenta[m]> | and is this in farmOS? or in a separate standalone app? or elsewhere? |
| [13:10:38] | <symbioquine[m]> | No, that's a separate/related concept |
| [13:11:28] | <symbioquine[m]> | I'm implementing a OpenLayers Interaction that encapsulates this idea of drawing polygons (starting with rectangles) relative to a line segment. |
| [13:12:12] | <mstenta[m]> | very cool! |
| [13:12:18] | <symbioquine[m]> | I'm hoping to then add a control/hook in farmOS-map to enable this "mode" |
| [13:12:54] | <paul121[m]> | we need behavior settings for farmOS-map :-) |
| [13:13:11] | <symbioquine[m]> | A "multi-area creation/editing" workflow could then take advantage of that or the snapping grid to easily draw lots areas. |
| [13:13:20] | <mstenta[m]> | yes!! |
| [13:13:27] | <symbioquine[m]> | but it would be a separate effort |
| [13:13:57] | <symbioquine[m]> | The point of this tool is just to make it practical to draw nice looking and precise areas/geometries from mobile. |
| [13:14:07] | <mstenta[m]> | i'm sort of envisioning a route with a full-width map and some behaviors that leverage farmOS 2.x's API for managing "locations" in bulk |
| [13:14:07] | <symbioquine[m]> | %s/tool/interaction/ |
| [13:14:23] | <mstenta[m]> | (for the multi-area tool) |
| [13:14:42] | <mstenta[m]> | and the "bed generator" feature could be a piece of it |
| [13:14:47] | <mstenta[m]> | (maybe the first piece) |
| [13:15:37] | <mstenta[m]> | one thing though... i wrote some custom PHP-based geometry stuff for doing the calculations... so i'm hoping that that can translate to JS |
| [13:16:00] | <symbioquine[m]> | that's actually kind of what I was working on before I got sidetracked on the touch drawing part; |
| [13:16:02] | <symbioquine[m]> | ACTION uploaded an image: (44KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/KQxaOGCutWImqFeU... > |
| [13:16:02] | <mstenta[m]> | (but if not i suppose we could leave it server side and have an endpoint for using it via JS AJAX requests or something) |
| [13:16:21] | <symbioquine[m]> | "A deep-linkable, map-centric, mobile-optimized tool for working with assets in farmOS" |
| [13:16:54] | <mstenta[m]> | that's a mouthful! i love it! :-D |
| [13:17:20] | <symbioquine[m]> | I'm not sure whether it will turn into something I can share any time soon though. |
| [13:17:59] | <mstenta[m]> | cool cool - well we have some pretty straightforward initial requirements in farmOS 2.x I think... happy to compare notes sometime! |
| [13:18:33] | <mstenta[m]> | but if it turns into a huge scope it may make sense to punt and just do a relatively straight port of the 1.x area generator module as a first step |
| [13:18:44] | <symbioquine[m]> | It's a generalization of what we use for managing a large rabbitry; |
| [13:18:50] | <symbioquine[m]> | ACTION uploaded an image: (157KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/DWHpkoUTrBrHgAaG... > |
| [13:19:12] | <mstenta[m]> | oh so cool |
| [13:19:44] | <symbioquine[m]> | Sorry if this is all kind of jumbled to share in a single linear chat thread... |
| [13:19:50] | <mstenta[m]> | > but if it turns into a huge scope it may make sense to punt and just do a relatively straight port of the 1.x area generator module as a first step |
| [13:19:50] | <mstenta[m]> | (this may end up being the more realistic thing) |
| [13:19:57] | <mstenta[m]> | no worries :-) |
| [13:20:32] | <mstenta[m]> | (that could be done in a few hours probably... hard to beat that... but now is our chance to think bigger too...) |
| [13:20:49] | <symbioquine[m]> | Yeah |
| [13:53:21] | * ssoyrnoz[m] has joined #farmos |
| [13:54:11] | <ssoyrnoz[m]> | Hello. I am a new user to FarmOS and I am just starting to explore the community and see what is possible with the software. |
| [14:03:02] | <ssoyrnoz[m]> | So far, I am finding it quite intuitive to use. I'm looking into hosting my own local version on a Raspberry Pi. I understand there is a FarmOS 2.x in the works. I was wondering if it would be worth the effort to get a server running and a DB populated on 1.x and migrate to 2.x or if 2.x beta release is "expected" (I understand this is a when it's done it's done kind of thing) sometime soon? I'm also hoping I can use some |
| [14:03:02] | <ssoyrnoz[m]> | of my scientific python skills to make some useful modules for statistical data analysis at some point. Thank you all for your work on the FarmOS software, it is amazing. |
| [14:03:33] | <mstenta[m]> | Hi ssoyrnoz ! Welcome! |
| [14:04:17] | <mstenta[m]> | > I was wondering if it would be worth the effort to get a server running and a DB populated on 1.x and migrate to 2.x or if 2.x beta release is "expected" |
| [14:04:17] | <mstenta[m]> | This probably boils down to: do you need to start using farmOS with real data? |
| [14:04:20] | <mstenta[m]> | If so, then start with 1.x |
| [14:04:43] | <mstenta[m]> | But if you're going to be experimenting with developments, python scripts, APIs, etc then definitely I recommend 2.x |
| [14:04:54] | <mstenta[m]> | You might even consider setting both up side-by-side! |
| [14:05:18] | <mstenta[m]> | The way the 2.x "migration" works is: you set up a second database and run a migration process to copy data from 1.x to 2.x |
| [14:05:40] | <mstenta[m]> | So in theory you could have both... where 1.x is your "canonical", but you automate the migration and use 2.x for experimentation |
| [14:05:59] | <mstenta[m]> | In terms of 2.x beta timeline... the hope is that it will be ready later this year |
| [14:06:07] | <mstenta[m]> | But yea... no guarantees ;-) |
| [14:07:19] | <ssoyrnoz[m]> | Kind of a bit of both really. I have a small livestock operation (~50 head goats/sheep) so real data is the goal. I'm not opposed to running two instances, I assume once one is up the second is simple enough? Is there a large difference between 1.x and 2.x API or is it something where a module or analysis package could be re-written easily to adjust between? |
| [14:08:03] | <mstenta[m]> | The 2.x API is much better/cleaner/more robust... |
| [14:08:25] | <mstenta[m]> | The data model itself isn't much different, so you could certainly do htings in 1.x and then update... But it's more work in the long run of course |
| [14:09:33] | <mstenta[m]> | We are documenting the API changes here: https://docs.farmos.org/development/api/changes/ |
| [14:09:55] | <paul121[m]> | The beta release of the farmOS.py library can communicate with both 1.x and 2.x servers. Although the data structure you'll get back will be different between the servers: https://github.com/farmOS/farmOS.py/releases/tag/v1.0.0-beta.1 |
| [14:09:56] | <ssoyrnoz[m]> | That's super helpful, ty :) |
| [14:10:41] | <ssoyrnoz[m]> | Thank you both |
| [14:17:05] | <ssoyrnoz[m]> | I know in theory the FarmOS server could be run on a raspberry Pi, but my forum searching didn't find much useful information about how well it runs or if there are known issues (beyond 32 bit). Do you know of anyone who has run the FarmOS on an Rpi? |
| [14:17:25] | <mstenta[m]> | Yes! It is definitely possible |
| [14:17:47] | <mstenta[m]> | There's a github thread that might be useful... |
| [14:18:01] | <mstenta[m]> | But basically, there are two approaches... Docker or not |
| [14:18:09] | <mstenta[m]> | Are you familiar with Docker, perchance? |
| [14:19:00] | <ssoyrnoz[m]> | Only lightly, I've been looking into that exact question for the last couple days. I was leaning towards docker but if the overhead is too much I would go without. |
| [14:19:32] | <mstenta[m]> | I'd recommend it |
| [14:19:43] | <mstenta[m]> | It encapsulates all the dependencies, so you have less to worry about |
| [14:19:52] | <mstenta[m]> | Decouples that from the server |
| [14:19:55] | <ssoyrnoz[m]> | Similar to a virtual env, if I understood it right? |
| [14:20:17] | <mstenta[m]> | Yea similar - it's basically a Linux box inside a Linux box :-) |
| [14:20:40] | <mstenta[m]> | So you can install things like Apache, PostgeSQL etc |
| [14:20:51] | <mstenta[m]> | Definitely recommend using Docker if you are going to run 1.x and 2.x side-by-side! |
| [14:21:24] | <mstenta[m]> | Here are the 2.x local dev environment setup guides: https://docs.farmos.org/development/environment/ |
| [14:21:44] | <mstenta[m]> | and here are the github threads I mentioned above: |
| [14:21:45] | <mstenta[m]> | https://github.com/farmOS/farmOS.org/issues/39 |
| [14:21:56] | <mstenta[m]> | https://github.com/farmOS/farmOS/issues/339 |
| [14:22:28] | <mstenta[m]> | the only challenge on raspberry pi right now is you have to build the docker image yourself |
| [14:22:42] | <mstenta[m]> | (not hard... but you can't pull from docker hub, because those are all i386 architecture images) |
| [14:23:09] | <mstenta[m]> | to be honest... you might want to experiment outside of raspberry pi as a first step... |
| [14:23:15] | <mstenta[m]> | just to limit the variables :-) |
| [14:23:34] | <mstenta[m]> | there may still be issues on Pi that haven't been discovered yet |
| [14:23:50] | <ssoyrnoz[m]> | Yeah, that seems like the way to go. My first attempt is already starting on a virtualbox running Ubuntu 20.04 |
| [14:24:52] | <ssoyrnoz[m]> | However making that run 24/7 is unrealistic |
| [14:25:17] | <symbioquine[m]> | Pi-gen can be really helpful too since you can do the computationally complex parts of the build on a faster emulated rPI: https://github.com/RPi-Distro/pi-gen |
| [14:26:14] | <symbioquine[m]> | You use it to build a image that you can write to your SD card and you could customize it to build the farmOS docker images as part of that. |
| [14:26:52] | <ssoyrnoz[m]> | That's also a good idea. I've tried that before using VB but making an ISO that transfers to an SD card without breaking has been a challenge in the past. |
| [14:29:32] | <symbioquine[m]> | ACTION posted a file: example.patch (6KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/YQGiqJxhgJkeWuQU... > |
| [14:29:58] | <symbioquine[m]> | ^ That's roughly what I was doing to get a image with docker/docker-compose pre-installed |
| [14:30:45] | <symbioquine[m]> | Based off the arm64 branch at commit 8808124cc319932f5fff4d8c5b78a9b6de95d642 |
| [14:32:30] | <symbioquine[m]> | Presumably, you'd then want to add a further stage to copy a directory with your Dockerfile and perform a `docker build` against it. |
| [14:35:36] | <ssoyrnoz[m]> | That file will take me a bit to digest, but seems like something I could do. I'm not a developer or anything but eventually I usually manage to cobble together something that works (maybe less twine than I use on the farm but same idea). |
| [14:37:12] | <symbioquine[m]> | Incidentally mstenta a similar strategy could be used to automatically build/test farmOS for arm64 without actually needing an arm device involved. |
| [14:38:41] | <ssoyrnoz[m]> | If, however, you want to use lasers to detect cow farts (via Raman hyperspectral imaging), I got you covered 🤣 |
| [14:38:43] | <mstenta[m]> | Cool! Yea I'm sort of excited about the ideas at the end of this thread in that regard: https://github.com/farmOS/farmOS/issues/339 |
| [14:39:20] | <mstenta[m]> | Now I want to hear more ssoyrnoz haha |
| [14:41:22] | <ssoyrnoz[m]> | Heh, it involves a lot of physics but basically you can use a laser to excite a gas cloud, and it will reflect the light at a slightly different wavelength based on the molecular composition. You can use that to detect methane, and with a fast enough spectrograph you can actually take a picture of the methane. I've seen this kind of instrument loaded on a drone and used to measure the methane emissions over farms to |
| [14:41:22] | <ssoyrnoz[m]> | quantify their greenhouse gas footprint. |
| [14:41:44] | <mstenta[m]> | wow! |
| [14:45:18] | <ssoyrnoz[m]> | Btw, have you looked into pulling live satellite data into the FarmOS map layers? You can get things like soil moisture and snow pack info from the NASA SMAP satellite, dust/smoke/particulate from NOAA GOES, wind and gasses from the ESA Sentinel missions. I believe all those are available online as GIS layers. |
| [14:45:44] | <mstenta[m]> | the farmOS-map library is built on OpenLayers - so a lot is possible! |
| [14:45:57] | <mstenta[m]> | you should write a module! :-D |
| [14:47:00] | <ssoyrnoz[m]> | I'll see what I can do. I assume the map modules available could be used as a template and just adjust things like the pointing location, name, etc? |
| [14:47:32] | <mstenta[m]> | yea! here's a simple example: https://github.com/farmOS/farm_map_no |
| [14:47:49] | <mstenta[m]> | that's for 1.x... we are working on the 2.x map stuff right now, but hope to have a similar example to work from soon |
| [14:48:49] | <ssoyrnoz[m]> | Good to know. Yeah, that looks easy enough assuming I can get a URL for the layer. |
| [14:49:06] | <mstenta[m]> | https://github.com/farmOS/farmOS-map#adding-layers |
| [14:50:06] | <ssoyrnoz[m]> | I did notice one thing with the map, and I assume it is a known issue? I drew my field lines using the default map (mapbox) but when I switched to Google satellite, everything had shifted about 20ft to the west. |
| [14:50:26] | <mstenta[m]> | hmm |
| [14:50:42] | <mstenta[m]> | that could actually be a google/mapbox imagery issue |
| [14:51:10] | <mstenta[m]> | that's actually the exact reason we made that farm_map_no module |
| [14:51:11] | <mstenta[m]> | someone in norway noticed that the google layers were not correct |
| [14:51:12] | <ssoyrnoz[m]> | That is what I figured. |
| [14:51:26] | <mstenta[m]> | he had GPS data from his tractor and it didn't line up with google |
| [14:51:28] | <symbioquine[m]> | <ssoyrnoz[m] "Good to know. Yeah, that looks e"> Most kinds of GIS servers have some sort of API/directory with the meta info about what layers are available |
| [14:51:37] | <mstenta[m]> | so we made that with the official norway layer and then it matched up |
| [14:51:54] | <mstenta[m]> | now i'm curious: where are you located? and i wonder which one is correct... mapbox or google? |
| [14:52:18] | <ssoyrnoz[m]> | Washington state, making a side by side comparison image, one min. |
| [14:52:37] | <symbioquine[m]> | e.g. https://github.com/symbioquine/farm_map_sjc/blob/7.x-1.x/farmOS.map.beha... |
| [14:52:44] | <symbioquine[m]> | https://gis.sanjuanco.com/arcgis/rest/services/Basemaps?f=pjson |
| [14:55:32] | <ssoyrnoz[m]> | ACTION uploaded an image: (1057KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/kxiLDHLeTVipoIwp... > |
| [14:55:55] | <mstenta[m]> | oh wow yea |
| [14:56:02] | <ssoyrnoz[m]> | Note the road on the right. I was wrong, image is shifted about 60 ft west |
| [15:13:19] | <ssoyrnoz[m]> | So, at least based on GPS and property map, it appears the Google imagery is more accurate than the Mapbox. |
| [15:13:34] | <mstenta[m]> | interesting! |
| [15:16:32] | <ssoyrnoz[m]> | Here's the problem, about a mile from my farm I found this, I'm assuming they just stitched the imagery together wrong in my location. |
| [15:16:36] | <ssoyrnoz[m]> | ACTION uploaded an image: (417KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ApVTRGSxZCSaXBOJ... > |
| [15:17:14] | <mstenta[m]> | ah there ya go :-) |
| [15:41:55] | <frakman1[m]> | <mstenta[m] "the only challenge on raspberry "> I just built the Dockerfile on my Pi and pushed it to my repo in dockerhub. Can that be used to help anyone? |
| [15:42:17] | <mstenta[m]> | Cool! |
| [15:42:23] | <mstenta[m]> | Yea perhaps! |
| [15:49:01] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/RolrhrRWwyvXCQeS... > |
| [15:49:30] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/ejPaoxeyvhrlCObO... > |
| [15:54:04] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/aHVnacwWBuIDSbSJ... > |
| [15:57:29] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/eUwneFgGJvrCcPyV... > |
| [15:58:08] | <mstenta[m]> | Hmm are you using the example `docker-compose.yml`? |
| [15:58:21] | <mstenta[m]> | (I have to step away in 2 minutes...) |
| [15:58:32] | <frakman1[m]> | yes, the development one. Let me add the full www logs... |
| [15:58:47] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/bfbwbGRmzhUIzQEg... > |
| [15:59:11] | <mstenta[m]> | What operating systme is the host? |
| [15:59:15] | <frakman1[m]> | I'm using: https://github.com/farmOS/farmOS/blob/7.x-1.x/docker/docker-compose.deve... |
| [15:59:19] | <mstenta[m]> | * What operating system is the host? |
| [15:59:47] | <mstenta[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/yDVxWDoKGSyJEYdo... > |
| [15:59:50] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/YPxtMTJmPmtmXgFP... > |
| [15:59:55] | <mstenta[m]> | (not a long-term solution!) |
| [15:59:57] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/GgmFmsmFloLxnGFh... > |
| [16:00:25] | <mstenta[m]> | those lines mount a local `www` directory in as a volume on `/var/www/html` (the apache document root) inside the container |
| [16:00:34] | <mstenta[m]> | seems to be an issue there... so testing without that will help to isolate |
| [16:00:41] | <mstenta[m]> | but ultimately you DO need to mount a volume |
| [16:00:49] | <mstenta[m]> | i'll be back later.... hope that helps! |
| [16:00:52] | <frakman1[m]> | do I need to create a folder structure in my local folder first? |
| [16:01:10] | <mstenta[m]> | no it should create that `www` folder automatically |
| [16:01:13] | <mstenta[m]> | but maybe that's the problem? |
| [16:02:15] | <frakman1[m]> | Yes, that worked, I now see the Drupal setup page |
| [16:05:32] | <frakman1[m]> | I removed www dir, uncommented the lines and re-ram docker-compose as root (sudo) but still th same problem. |
| [16:05:41] | <frakman1[m]> | * I removed www dir, uncommented the lines and re-ran docker-compose as root (sudo) but still th same problem. |
| [16:43:10] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/iAYgXONmupmPTUWY... > |
| [16:43:56] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/atVAwHRZeNcEVpQq... > |
| [17:01:02] | <frakman1[m]> | `/var/www/html` currently only has a `sites` directory. |
| [17:01:02] | <frakman1[m]> | When I manually untar'd the file `farm-7.x-1.x-dev-core.tar.gz` sitting in /tmp into /var/www/html/ like in the ``Dockerfile`` here: https://github.com/farmOS/farmOS/blob/c5c15043cf30275fa1bdadf8e39a9393ff... |
| [17:01:02] | <frakman1[m]> | Everything worked again. For some reason this part isn't happening automatically |
| [17:01:27] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/MPLwhipXwvepYsYn... > |
| [17:01:39] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/ApUyracxMvviPqDj... > |
| [17:05:28] | <mstenta[m]> | Ah hmm - so we have a script `docker-entrypoint.sh` that should run when the container starts which takes care of checking if that directory is empty and copying the files over |
| [17:05:32] | <mstenta[m]> | https://github.com/farmOS/farmOS/blob/7.x-1.x/docker/docker-entrypoint.sh |
| [17:05:35] | <mstenta[m]> | maybe that didn't run for some reason? |
| [17:06:41] | <frakman1[m]> | I think the logic is wrong though. |
| [17:06:41] | <frakman1[m]> | `if ! [ "$(ls -A /var/www/html/sites/)" ]; then` |
| [17:06:41] | <frakman1[m]> | that folder exists and has a few things. But the folder that matters is everything around sites in the same folder(/var/www/html) |
| [17:07:00] | <frakman1[m]> | * I think the logic is wrong though. |
| [17:07:00] | <frakman1[m]> | `if ! [ "$(ls -A /var/www/html/sites/)" ]; then` |
| [17:07:00] | <frakman1[m]> | that folder exists and has a few things. But the folder that matters is everything around `sites` in the same folder(`/var/www/html`) |
| [17:07:59] | <frakman1[m]> | * I think the logic is wrong though. |
| [17:07:59] | <frakman1[m]> | `if ! [ "$(ls -A /var/www/html/sites/)" ]; then` |
| [17:07:59] | <frakman1[m]> | that folder exists and has a few things (so it's not empty). But the folder that matters is everything around `sites` in the same folder(`/var/www/html`) |
| [17:08:32] | <mstenta[m]> | Oh oops I meant to link to the dev one |
| [17:08:47] | <mstenta[m]> | https://github.com/farmOS/farmOS/blob/7.x-1.x/docker/dev/docker-entrypoi... |
| [17:08:58] | <mstenta[m]> | (in 2.x we've merged these together) |
| [17:09:29] | <mstenta[m]> | In dev environments you want the whole codebase mounted |
| [17:09:39] | <mstenta[m]> | But in production you may only want sites |
| [17:11:05] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/tauONMVJDPnHvCSt... > |
| [17:14:09] | <frakman1[m]> | I think I see what happened. I ran `docker build` from the `docker` folder instead of the `docker/dev/` folder which is needed if I then run `docker-compose.development.yml` |
| [17:21:47] | <frakman1[m]> | ACTION < https://matrix.org/_matrix/media/r0/download/matrix.org/FGjbgFQkQMOflMHa... > |
| [18:04:12] | <mstenta[m]> | Oh yes ok... |
| [18:05:01] | <mstenta[m]> | So... You need to first build the base image, and tag it as farmos/farmos |
| [18:05:21] | <mstenta[m]> | Then build the dev image, and tag it as farmos/farmos:dev |
| [18:05:30] | <mstenta[m]> | With the -t flag |
| [18:05:44] | <mstenta[m]> | That will essentially override the docker hub tag |
| [18:05:51] | <mstenta[m]> | So that it uses the local image instead |
| [18:05:56] | <mstenta[m]> | If that makes sense? |
| [18:10:30] | <frakman1[m]> | Yes. Thanks. I'll give that a go. |
| [18:13:20] | <frakman1[m]> | How are docker images being built now? Is there a CICD pipeline somewhere? |
| [18:13:20] | <frakman1[m]> | Are you familiar with the buildx option to docker? |
| [18:13:51] | <frakman1[m]> | * How are docker images being built now? Is there a CICD pipeline somewhere? |
| [18:13:51] | <frakman1[m]> | Are you familiar with the `buildx` option to docker? |
| [18:14:28] | <frakman1[m]> | It should allow docker build to make an image for multiple architectures including `linux/arm/v7` |
| [18:14:40] | <frakman1[m]> | * It should allow `docker build` to build an image for multiple architectures including `linux/arm/v7` |
| [18:17:17] | <frakman1[m]> | The idea is that the single, official farmOS docker-hub image should be Pi-compatible. |
| [19:02:21] | <mstenta[m]> | We're using docker hubs options now but.... |
| [19:02:23] | <mstenta[m]> | https://github.com/farmOS/farmOS/issues/339 |
| [19:02:43] | <mstenta[m]> | 🙌 |
| [19:02:50] | <mstenta[m]> | I'm excited for that! |
| [19:38:45] | <frakman1[m]> | > You need to first build the base image, and tag it as farmos/farmos |
| [19:38:45] | <frakman1[m]> | > Then build the dev image, and tag it as farmos/farmos:dev |
| [19:38:45] | <frakman1[m]> | Which Dockerfile for each? |
| [19:39:24] | <frakman1[m]> | Is this the base? |
| [19:39:24] | <frakman1[m]> | https://github.com/farmOS/farmOS/blob/7.x-1.x/docker/Dockerfile |
| [19:39:41] | <frakman1[m]> | And this the dev? |
| [19:39:41] | <frakman1[m]> | https://github.com/farmOS/farmOS/blob/7.x-1.x/docker/dev/Dockerfile |
| [19:39:47] | <mstenta[m]> | Yes |
