| [20:21:26] | * JustTB has quit (Ping timeout: 258 seconds) |
| [00:02:54] | * JustTB has joined #farmos |
| [02:39:14] | * JustTB has quit (Quit: Leaving.) |
| [04:27:36] | * JustTB has joined #farmos |
| [04:31:38] | * msandstrom[m] has joined #farmos |
| [04:46:00] | <msandstrom[m]> | Hi! just started to use farmos at our farm and thank you for creating this. As a programmer myself and with a wife into business management we easily see the benefits of the system. However, we have a multitude of additional systems around the farm (for example emoncms for environmental monitoring, cameras for monitoring and DVR, solarpanels connected to SolarEdge API and LoRa for controlling equipment). While we don't |
| [04:46:01] | <msandstrom[m]> | expect farmOS to replace this we would certainly would to include this information into farmOS dashboards and/or control. Using Drupal modules seems to be a logical way to do this but then I have to ask if there is any architectural documentation of farmOS available so my modules would fit nicely into the overall system. Thanks! |
| [08:15:48] | <mstenta[m]> | Hi @msandstrom |
| [08:16:09] | <mstenta[m]> | We need more of that kind of documentation |
| [08:16:28] | <mstenta[m]> | In the meantime I'd be happy to answer any questions you have |
| [08:18:00] | <msandstrom[m]> | <mstenta[m] "In the meantime I'd be happy to "> Thanks. First thing would be to understand where to locate my own modules (I guess under /contrib) and the second is naming - is "farm_*" approved or recommended? Should I go with something else? |
| [08:21:35] | <mstenta[m]> | Put modules in sites/all/modules |
| [08:21:49] | <mstenta[m]> | Not in profiles/farm/modules |
| [08:22:10] | <mstenta[m]> | Because that should be left alone so you can easily replace it with upgrade versions |
| [08:22:37] | <mstenta[m]> | Basically, everything in the sites directory will persist between upgrades |
| [08:22:51] | <mstenta[m]> | Everything outside of that can then be replaced with the new version |
| [08:23:34] | <mstenta[m]> | As for module namespacing, that's up to you, but yes I like to prefix with farm_ |
| [08:24:03] | <mstenta[m]> | To signify that it's a farmOS extension, and not just a drupal module more generally |
| [08:25:02] | <mstenta[m]> | (these would be great things to start documenting on farmOS.org, if you are interested in starting that! Or even just starting a GitHub issue for it) |
| [08:27:19] | <msandstrom[m]> | Thanks! This would at least get me started - the learning curve for Drupal seems to be steep (I'm developing mainly in CodeIgniter). I'll start to see if I can manage to get the surveilance cameras displayed on a separate tab in the dashboard, that would make my day :-) |
| [08:27:31] | <mstenta[m]> | Great! |
| [08:27:43] | <mstenta[m]> | Yea Drupal can take some getting used to |
| [08:28:00] | <mstenta[m]> | But I can point to examples to help get you going |
| [08:28:18] | <mstenta[m]> | Take a look at this one, perhaps: |
| [08:28:54] | <mstenta[m]> | https://github.com/mstenta/farm_sensor_atmospi |
| [08:29:06] | <mstenta[m]> | Might be similar to what you have in mind |
| [08:30:19] | <mstenta[m]> | Very simple example that adds a new type of sensor, with custom config for it |
| [08:30:35] | <mstenta[m]> | And basically just adds an iframe to the sensor page in farmOS |
| [08:31:04] | <mstenta[m]> | So you could consider your cameras a new type of sensor perhaps |
| [08:31:18] | <msandstrom[m]> | Cool! Sensors are important and the idea of collecting the read-outs into farmOS is very compelling, not necessary for logging but for accessability. |
| [08:32:00] | <mstenta[m]> | Yes! And the atmospi module is a good example for that too because it doesn't actually collect data into farmOS |
| [08:32:08] | <mstenta[m]> | It just integrates the sensor |
| [08:32:14] | <mstenta[m]> | So you can view it |
| [08:33:53] | <msandstrom[m]> | Yes. We have a long holiday compining up here in Sweden so let's see if I can get anything working. Thank you again. (And thank for your support with Clean URLs earlier this week). |
| [08:34:12] | <msandstrom[m]> | Yes. We have a long holiday comining up here in Sweden so let's see if I can get anything working. Thank you again. (And thank for your support with Clean URLs earlier this week). |
| [08:34:16] | <mstenta[m]> | My pleasure |
| [08:34:18] | <mstenta[m]> | Good luck! |
| [08:34:27] | <mstenta[m]> | And happy holiday weekend :-) |
| [08:47:25] | <mstenta[m]> | Oh! And thanks for contributing to the open collective msandstrom !!! I just made the connection! :-) |
| [08:49:04] | <msandstrom[m]> | Happy to be part of the community. |
| [09:11:11] | <skipper_is[m]> | Oh I like the camera idea! I need to get my head around extensions as well, would like to integrate my RFID scanner |
| [09:11:33] | <mstenta[m]> | That would be great skipper_is ! |
| [09:12:10] | <mstenta[m]> | I'd love to see a more flexible asset ID system in general, which allows assigning different kinds of IDs (eg: RFID, QR codes, barcodes, etc) to any asset |
| [09:12:41] | <msandstrom[m]> | <skipper_is[m] "Oh I like the camera idea! I nee"> If I get anything working I'll be sure to document it. |
| [09:13:01] | <mstenta[m]> | This is relevant: https://www.drupal.org/project/farm/issues/2396617 |
| [09:15:50] | <msandstrom[m]> | <mstenta[m] "This is relevant: https://www.dr"> We have already added simple QR-codes pointing directly into our farmOS installation. The next step for that was to create a middle-where where we could do quick enter of data (such as fueling and run-hours) and then post data using API into farmOS. This is of course made in CodeIgniter... |
| [09:16:08] | <mstenta[m]> | cool! |
| [09:16:29] | <mstenta[m]> | msandstrom: have you seen the farmOS android/iOS app yet? |
| [09:16:55] | <mstenta[m]> | it's still pretty new, but i envision a lot of stuff like that being developed there eventually |
| [09:22:01] | <msandstrom[m]> | <mstenta[m] "msandstrom: have you seen the fa"> Haven't had a chance to look at that yet. |
| [09:27:20] | <skipper_is[m]> | I can't get it to work on my S7... |
| [09:41:36] | <dornawcox[m]> | mstenta: regarding barcodes and inventory for the transition to point of sale systems/transactions we were looking at adapting https://github.com/opensourcepos/opensourcepos. It was apealing because it already has support for scales/weights and barcodes and is PHP and MySQL based. Have not dug deeply yet. |
| [11:22:52] | <johanness_charle> | Hello, how do I get read of "You are not authorized to access this page." |
| [11:27:44] | <mstenta[m]> | johanness_charles: are you logged in? |
| [11:34:58] | <johanness_charle> | <mstenta[m] "johanness_charles: are you logge"> This appears to Authenticated user and Anonymous user |
| [11:39:29] | <johanness_charle> | Is there any means that I can disable that to site visitors and even authenticated users ? |
| [13:00:22] | * JustTB has quit (Ping timeout: 244 seconds) |
| [14:37:36] | <mstenta[m]> | @johanness_charles that is the default access denied text |
| [14:37:48] | <mstenta[m]> | That comes from Drupal's access control system |
| [14:38:26] | <mstenta[m]> | I'm not sure I understand removing it. Do you mean you want to allow public access to your farmOS? |
| [14:38:41] | <mstenta[m]> | Or you just want to change that specific text? |
| [14:38:42] | * JustTB has joined #farmos |
| [17:16:36] | <johanness_charle> | <mstenta[m] "That comes from Drupal's access "> Ok, thank you. I was my fault i was not using the user initials after my domain. http://mydomain/?q=user |
| [17:16:49] | <johanness_charle> | Now it is ok |
| [17:23:55] | <johanness_charle> | How do I enable Secure (HTTPS) connection on my Drupal farmOS platform ? |
| [17:25:08] | <mstenta[m]> | johanness_charles: you would configure that on the server level... eg: in Apache |
| [17:25:14] | <mstenta[m]> | or Nginx, depending on what you're using |
| [17:25:44] | <mstenta[m]> | this might be a good place to start: https://www.drupal.org/https-information |