IRC logs for #farmOS, 2019-02-10 (GMT)

2019-02-09
2019-02-11
TimeNickMessage
[22:30:03]* JustTB has quit (Ping timeout: 245 seconds)
[22:46:10]* JustTB has joined #farmos
[05:56:45]* JustTB has quit (Quit: Leaving.)
[06:05:43]* JustTB has joined #farmos
[07:21:07]* JustTB has quit (Quit: Leaving.)
[07:22:02]* JustTB has joined #farmos
[07:31:50]* JustTB has quit (Quit: Leaving.)
[08:22:29]* JustTB has joined #farmos
[15:13:07]* berryfarmer[m] has joined #farmos
[15:14:08]<berryfarmer[m]>Hello to the farmOS team. Thanks for the great tool for the farming community.
[15:15:54]<berryfarmer[m]>How far of is the release of rc3? Just wondering because updating rc2 always runs into missing modules problem. I can copy the missing modules into the profile and other folders resolving the issues but thats probably not the intended way to update, or is it?
[15:16:53]<mstenta[m]>Hi berryfarmer - welcome!
[15:17:10]<mstenta[m]>What do you mean by missing modules?
[15:19:05]<berryfarmer[m]>I am new to drupal so not sure if I do something wrong. I ran the update via ssh and ended up with a lot of "unresolved dependencies" like restws_file, openlayers_geofiled, openlayers_libary (Missing)
[15:19:25]<mstenta[m]>Ah
[15:19:55]<berryfarmer[m]>So I am a bit scared to input my data into rc2 and break the site during the rc3 update ;)
[15:20:15]<mstenta[m]>Did you read this? https://farmos.org/hosting/updating/
[15:20:49]<mstenta[m]>It is not recommend to update modules manually
[15:21:02]<berryfarmer[m]>yes I did, this is a great option but I would like to keep the data on my own server.
[15:21:16]<mstenta[m]>Because farmOS includes patches to a number of modules that it uses
[15:21:28]<mstenta[m]>Which will not be included if you update Mahajan
[15:21:34]<mstenta[m]>Manually*
[15:21:45]<mstenta[m]>That documentation is for self hosting
[15:22:21]<berryfarmer[m]>I would rather pay a one time "fee" to support you and the development.
[15:22:32]<mstenta[m]>The link I pasted is the instructions for updating farmOS if you are hosting it yourself
[15:23:23]<berryfarmer[m]>sorry I just read the link, it was a differnt one than the hosting site
[15:24:15]<mstenta[m]>> farmOS is a Drupal distribution, and includes patches to some contributed Drupal modules that are necessary for proper functioning. Drupal's automatic update feature will not apply the necessary patches when it downloads the new version of a module.
[15:24:16]<mstenta[m]>It also does not support updating Drupal distributions (only modules and themes). farmOS is a Drupal distribution, and new versions often include automated update code to ensure a smooth update from one version of farmOS to the next.
[15:24:17]<mstenta[m]>Therefore, it is recommended that you either download the officially packaged releases of farmOS from https://drupal.org/project/farm, build it yourself with Drush, or run farmOS on Docker. This will ensure that the necessary patches are applied, and that the farmOS distribution updates are included.
[15:25:16]<mstenta[m]>But with all that in mind... If you are using rc2 then you don't need to worry about updating until rc3 comes out
[15:25:20]<berryfarmer[m]>ok. so using the update from within the reports site of farm os is not the best way to do this
[15:25:32]<mstenta[m]>If you are having issues with rc2, that that is a separate concern
[15:25:44]<mstenta[m]>Correct. That will break your site
[15:26:05]<berryfarmer[m]>rc2 runs fine just the update was the problem.
[15:27:18]* farmBOT has joined #farmos
[15:27:21]<mstenta[m]>Yes, it's a bit tricky because Drupal provides the auto update features, but they can cause issues in the case of a distribution like farmOS
[15:27:49]<berryfarmer[m]>Thank You Mike for the quick response!
[15:28:12]<mstenta[m]>It might be worth us trying to hide that feature of Drupal to prevent this kind of issue in the future
[15:28:20]<berryfarmer[m]>Thats really good to know!
[15:29:44]<berryfarmer[m]>Yeah runing updates is sometimes tempting to get new exciting features
[15:30:55]<mstenta[m]>Yea true - in this case when it says there are updates available it is referring to the non-farmOS modules that serve as the building blocks
[15:31:51]<mstenta[m]>It is possible to stay up to date on the latest farmOS features too, without waiting for the next release... But that definitely requires some experience with Drupal to know how
[15:32:17]<mstenta[m]>So the safest thing to do is just wait for the release
[15:32:17]<berryfarmer[m]>Ah I see. So usually you push your updates via betas or rc's?
[15:32:50]<mstenta[m]>(and if there's something in particular that you're waiting for, poke me and tell me to make a new release) ;-)
[15:33:57]<mstenta[m]>Well I push all changes to the main branch of the git repository, and then when it's time for a new release I will tag and package that so it's available for download on drupal.org and GitHub
[15:34:29]<berryfarmer[m]>There are a lot of different things one could wish for but I found that you already included a lot of very good features into rc2 comming from rc1 which I installed first.
[15:34:50]<mstenta[m]>So technically you can follow the main branch and get new commits as they are created, but then you may also have to rebuild farmOS if there are any module updates or patches includes t
[15:35:04]<mstenta[m]>Oh great! Glad to hear it!
[15:35:18]<mstenta[m]>And yes we do have a long feature request list! :-)
[15:35:44]<mstenta[m]>Lots of great ideas to keep us busy
[15:36:34]<berryfarmer[m]>you guys really created a great tool for the farming community espacially those with smaller farms
[15:36:54]<mstenta[m]>Thanks! Glad you find it useful!
[15:37:49]<berryfarmer[m]>I will keep recommending it to friends and people from the farming community and hope it gets many more users!
[15:38:00]<mstenta[m]>Awesome thanks!
[15:38:17]<mstenta[m]>Well feel free to ask questions here anytime
[15:38:32]<mstenta[m]>Especially when it comes time to update to rc3 ;-)
[15:39:12]<berryfarmer[m]>Thank you! And thank you for your time answering my newbie questions ;)
[15:39:30]<mstenta[m]>My pleasure