| [05:07:36] | <Spixmaster[m]> | mstenta: I replied on Github, https://github.com/farmOS/farmOS/issues/790#issuecomment-1948084213. I did not respond there because I wanted to wait until I make an account on the farmOS forum as I assumed you wanted to hold the discussion in the forum as implied in your last sentence.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/rNXRdQqWRDRTjBdA...) |
| [05:07:56] | <Spixmaster[m]> | s/in/there/, s/the forum// |
| [05:14:24] | <Spixmaster[m]> | To further address your concerns, the build instructions are [open source](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=farmos) and no source code despite needed changes to the configuration are done. |
| [05:14:24] | <Spixmaster[m]> | Almost all packages are not maintained by the responsible developers. I do not think anyone would assume to find official packages in the AUR. |
| [05:14:24] | <Spixmaster[m]> | The Arch Linux package management system tracks the files of each package. Those are simply the files that are put into the file system by that particular package. As setting and data files are created by the programme after the installation they are not tracked by pacman. Therefore when updating the package, the data and settings are not overwritten but only the source code. |
| [05:16:03] | <Spixmaster[m]> | mstenta: Concerning the updating, is it needed to call /update.php after an update or will the programme automatically detect that a database update or whatever is necessary? |
| [06:16:10] | <mstenta[m]> | Thanks for all the details Spixmaster! |
| [06:16:44] | <mstenta[m]> | It is necessary to call `/update.php` after an update, yes. It is also necessary to clear caches after that. This can be done via command line using `drush updb && drush cr` |
| [06:16:54] | <mstenta[m]> | As described here: https://farmos.org/hosting/update/ |
| [06:21:21] | <Spixmaster[m]> | mstenta[m]: Thanks, I will add the instructions to the PKGBUILD either as a message or by executing the commands. |
| [06:22:29] | <Spixmaster[m]> | mstenta: What about your initial concerns about the integrity of the package, updates or elese? Is there any doubt left? |
| [06:23:24] | <Spixmaster[m]> | s/elese/else/ |
| [06:40:13] | <Spixmaster[m]> | mstenta: The [package](https://aur.archlinux.org/packages/farmos) was just updated. |
| [06:48:11] | <mstenta[m]> | Spixmaster: That's great! |
| [06:49:26] | <mstenta[m]> | I would highly recommend taking a database snapshot before upgrading as well. I suppose that would be harder to automate, though, since it depends on what type of database the user will have (MariaDB/PostgreSQL/SQLite) |
| [06:49:54] | <mstenta[m]> | We always try to ensure that database updates run smoothly, but if there is a bug it can leave farmOS in a broken state. |
| [06:50:02] | <mstenta[m]> | So taking a snapshot before is critical. |
| [06:50:16] | <mstenta[m]> | Because then you can easily roll back and fix the issue before trying again. |
| [06:51:19] | <mstenta[m]> | > What about your initial concerns about the integrity of the package, updates or else? Is there any doubt left? |
| [06:51:19] | <mstenta[m]> | I trust your integrity! And thanks for helping me to understand the Arch user repository process. Would you be opposed to adding "(unofficial)" to the name of the package just to make it extra clear to potential users? |
| [06:52:23] | <Spixmaster[m]> | mstenta[m]: You are right. As the database is not fixed, that is impossible to automate. I think this falls under the competence of the administrator taking proper backups. |
| [06:53:29] | <mstenta[m]> | Is there a way to add a message before updating, which gives them a yes/no prompt to proceed? |
| [06:54:12] | <mstenta[m]> | Something like "It is important to take a database snapshot before updating farmOS, and to run update.php and clear caches after updating. See https://farmos.org/hosting/update/. Proceed? Y/N" |
| [06:55:24] | <mstenta[m]> | These are just suggestions to improve your package update experience for yourself and others. I don't want anyone to have a bad time. :-) |
| [06:56:05] | <Spixmaster[m]> | mstenta[m]: > <@mstenta:matrix.org> > What about your initial concerns about the integrity of the package, updates or else? Is there any doubt left?... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/ifgoquccEYDatCUM...) |
| [06:57:49] | <mstenta[m]> | How about in pkgdesc? |
| [06:58:10] | <Spixmaster[m]> | mstenta[m]: Prompts are explicitly prohibited, see https://wiki.archlinux.org/title/Creating_packages#Warnings the second bullet point. |
| [06:58:39] | <mstenta[m]> | Hmm OK. Well in that case it might be dangerous to run drush updb and drush cr without the user knowing. |
| [06:59:08] | <mstenta[m]> | It might be better for that to be an intentional step on their part. |
| [06:59:53] | <mstenta[m]> | (This is why we have detailed update instructions at https://farmos.org/hosting/update/ - there are some inherent complexities which are hard to automate in all situations) |
| [07:01:17] | <Spixmaster[m]> | mstenta[m]: Fine, I will remove the database and cache update. |
| [07:02:28] | <mstenta[m]> | I have to go now... it's morning and the kids need to get ready for school. I'll check back later. :-) |
| [07:02:35] | <Spixmaster[m]> | mstenta[m]: That would be really uncommon and is not intended, https://wiki.archlinux.org/title/PKGBUILD#pkgdesc. Almost every package is unofficial. |
| [07:08:40] | <Spixmaster[m]> | * is unofficial. Let me write that information into a comment and pin it. |
| [07:11:34] | <Spixmaster[m]> | <Spixmaster[m]> "That would be really uncommon..." <- [Pinned message](https://aur.archlinux.org/packages/farmos#comment-956718). |
| [07:23:28] | <mstenta[m]> | That makes sense |
| [07:23:41] | <mstenta[m]> | Looks great! Thanks Spixmaster! |
| [14:32:08] | <botlfarm[m]> | Curious if there is any start to a grazing plan contrib that anyone is aware of? There is a grant opportunity that is open to me to get students to work on innovative farming projects. Reading the requirements a grazing contrib module may qualify. I don't want there to be overlap in work if someone is already working on this, but if not I will apply. |
| [14:33:11] | <mstenta[m]> | botlfarm: We had one in v1! https://github.com/farmOS/farm_grazing |
| [14:33:21] | <mstenta[m]> | Hasn't been ported to v3 though (yet) |
| [14:33:58] | <mstenta[m]> | Happy to brain dump sometime! I made that back in 2017 and would have done a lot of things differently if I had the chance :-) |
| [14:34:51] | <botlfarm[m]> | Thanks mstenta. Yeah I used that for a while in v1 and loved some aspects of it but think it could be redone much better. |
| [14:35:16] | <botlfarm[m]> | This is a simple application I will fill out and we will see where it goes. |
| [14:35:47] | <mstenta[m]> | There might be some good overlap opportunities with the new crop planning module! |
| [14:36:36] | <mstenta[m]> | ACTION uploaded an image: (193KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/PKIdBRjpQjVPvusm... > |
| [14:36:57] | <mstenta[m]> | paul121 and I are designing these "timeline gantt charts" in a way that can be reused in other places |
| [14:37:22] | <botlfarm[m]> | very nice! |
| [14:37:22] | <mstenta[m]> | (Right now still pretty hard-coded to the crop planning module, but planning ahead...) |
| [14:38:05] | <botlfarm[m]> | This "grant" is targeting September 2024 schoolyear students so it is a bit out |
| [14:38:36] | <mstenta[m]> | Oh cool - well maybe we'll have some more stuff to play with by then too :-) |
| [14:38:57] | <mstenta[m]> | I'm really eager to add these timelines to the top of every asset page in farmOS core |
| [14:39:17] | <mstenta[m]> | So you can see where an asset will be, and all the logs associated with it |
| [14:40:13] | <mstenta[m]> | (eg: look at the roma tomato example in the pic above... that has different colored circles for each log type... seeding/transplanting, input, harvest... and empty/filled circles to represent pending/done) |
| [14:40:35] | <mstenta[m]> | (imagine something like that at the top of the 2024 Roma Tomato asset page itself!) |
| [14:41:01] | <botlfarm[m]> | That would be really cool |
| [14:41:39] | <mstenta[m]> | It's really close to possible! We've been experimenting with all the pieces in the crop plan... so it'll just be a matter of working some of that into a core PR |
| [14:42:26] | <mstenta[m]> | And then "plans" will just be able to show multiple of them basically... (and also customize for planning purposes specifically... like the crop plan doesn't just show locations, it also shows "stages" like seeding stage, transplanting stage, harvest stage, etc) |
| [14:43:31] | <mstenta[m]> | Grazing plans could show "grazing" and "recovery" stages, like the v1 module, perhaps |
| [14:44:05] | <botlfarm[m]> | I like it |
