farmos / farmos

farmOS: A web-based farm record keeping application.

farmOS

farmOS is a web-based application for farm management, planning, and record keeping. It is developed by a community of volunteers and aims to provide a standard platform for farmers, developers, and researchers to build upon.

Official website: farmOS.org

GETTING STARTED

If you would like to install and host farmOS yourself, see the official documentation on farmOS.org: https://farmOS.org/hosting/install

If you would like to pay for hosting, Farmier provides affordable options for individual farms and organizations.

MAINTAINERS

Current maintainers:

• Michael Stenta (m.stenta) - https://drupal.org/user/581414

This project has been sponsored by:

• Farmier
• Cornell University
• Vermont Agency of Agriculture Food & Markets
• Vermont Housing & Conservation Board
• UVM Extension
• Globetrotter Foundation
• Vermont Vegetable and Berry Growers Association
• Pennsylvania Association for Sustainable Agriculture
• Natural Resources Conservation Service
• The United States Forest Service - International Programs
• The National Forestry Authority of Uganda
• Our Sci
• Bionutrient Food Association
• Foundation for Food and Agriculture Research
• PVAMU College of Agriculture and Human Sciences
• Rothamsted Research
• OpenTEAM
• Wolfe's Neck Center for Agriculture and the Environment

CONTRIBUTORS

This project exists thanks to all the people who contribute.

OPENCOLLECTIVE BACKERS

Thank you to all our OpenCollective backers! [Become a backer]

OPENCOLLECTIVE SPONSORS

Support this project by becoming an OpenCollective sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

farmos's Issues

Add GEOS library via Dockerfile

The Area Generator module relies on the GEOS library. In order for that module to be usable in Docker containers, we will need to include that library via the Dockerfile.

There is an existing todo in the farmOS.org repository to add documentation for installing GEOS: farmOS/farmOS.org#9

See my comment here for more information: https://www.drupal.org/node/2736221#comment-11243999

Native app front end for farmOS

I am hoping to begin work soon on a farm recordkeeping app for Andriod and iOS that could serve as a front end for farmOS. The app would have its own database, stored on the phone, and would periodically synch records with farmOS. This would allow users to keep records in the field even if they do not have wifi or data access.

The main things that I hope users can accomplish with this app are

• Schedule and record routine farm activities including seeding, planting, crop maintenance and harvesting. This includes providing an easy to use harvest checklist for workers in the field.
• Keep records of the plantings, inputs and activities in each field/ farm area
• Keep track of area planed and amount harvested for each planting (i.e. crop yield)
• Keep track of the time invested in each activity (both person time and equipment time)
• Take text and photo notes, and associate them with fields and/ or plantings

The app would greatly expand on a labor tracking app for small farmers that I have already created called BeetClock - www.beetclock.com. My idea is that the app could work as a stand-alone, but could also serve as a front end for farmOS. I may also use Google Sheets as an alternate data back end, which is the approach I've taken in BeetClock.

I would plan to use a data structure similar to that of farmOS, based around assets and logs. The native app would deal with a more limited set of asset than farmOS, at least in the beginning.

Most of the information that I hope to track with the app can already be captured by farmOS, with the exception of time invested in each activity. If farmOS folks are interested in integrating labor tracking into farmOS, I would be glad to contribute!

Communication between the native app and farmOS:

The recordkeeping app would need to periodically synch records with the farmOS database. I am not sure exactly how this would work, but I am imagining the app would need to do something like the following:

• Sign in as a farmOS user
• Get new assets from farmOS (assets added to farmOS but not yet present in the native app)
• Get new logs from farmOS
• Send new assets to farmOS (assets created by the app user but not yet present in farmOS)
• Send new logs to farmOS

Before I start work on the app, I would like to learn more about the farmOS API and what it would take to get the app and farmOS to talk with one another. I've heard that there is a farmOS API or will be soon, but I've not been able to find any documentation on it. Would you be able to point me towards any resources that currently exist?

Also, I want to say that I'm very open to ideas and suggestions about what would make the app most useful, or how it could work best with farmOS. I'm excited about the project, and I look forward to working with the farmOS community!

Docker entrypoint is run every time container is started

I misunderstood the way that Docker's ENTRYPOINT scripts work - I thought they only ran when a container is initially created, but in fact they run every time the container is started. In hindsight, this makes more sense.

With this in mind, I will change the way that the entrypoint.sh works. Otherwise it will be rebuilding the farmOS codebase every time - which is both time consuming, and error prone.

`drush qd --makefile=build-farm.make` fails

 /.../Desktop/farmos ♘ drush qd --help | less
 /.../Desktop/farmos ♘ git clone [email protected]:farmOS/farm.git
Cloning into 'farm'...
remote: Counting objects: 716, done.
remote: Total 716 (delta 0), reused 0 (delta 0), pack-reused 716
Receiving objects: 100% (716/716), 106.09 KiB | 0 bytes/s, done.
Resolving deltas: 100% (444/444), done.
Checking connectivity... done.
 /.../Desktop/farmos ♘ cd farm/
 /.../farmos/farm[7.x-1.x] ♘ ls
README.md       build-farm.make     drupal-org-core.make    drupal-org.make     farm.info       farm.install        farm.profile
 /.../farmos/farm[7.x-1.x] ♘ drush qd --make=build-farm.make
Unknown option: --make.  See `drush help core-quick-drupal` for available options. To suppress this error, add the option --strict=0.                                     [error]
 /.../farmos/farm[7.x-1.x] ♘ drush qd --makefile=build-farm.make
Beginning to build build-farm.make.                                                                                                                                       [ok]
drupal-7.41 downloaded.                                                                                                                                                   [ok]
drupal patched with php_5_5_imagerotate-2215369-51.patch.                                                                                                                 [ok]
Generated PATCHES.txt file for drupal                                                                                                                                     [ok]
farm cloned from http://github.com/farmOS/farm.git.                                                                                                                       [ok]
Checked out branch 7.x-1.x.                                                                                                                                               [ok]
Found makefile: drupal-org.make                                                                                                                                           [ok]
colorbox-7.x-2.10 downloaded.                                                                                                                                             [ok]
Found makefile: colorbox.make                                                                                                                                             [ok]
colorbox downloaded from https://github.com/jackmoore/colorbox/archive/1.x.zip.                                                                                           [ok]
Project ctools contains 10 modules: views_content, term_depth, stylizer, page_manager, ctools_plugin_example, ctools_custom_content, ctools_ajax_sample, ctools_access_ruleset, bulk_export, ctools.
ctools-7.x-1.9 downloaded.                                                                                                                                                [ok]
ctools patched with eventBubblingBugIE8-1823088-9.patch.                                                                                                                  [ok]
Generated PATCHES.txt file for ctools                                                                                                                                     [ok]
Project date contains 11 modules: date_views, date_tools, date_repeat_field, date_repeat, date_popup, date_migrate_example, date_migrate, date_context, date_api, date_all_day, date.
date-7.x-2.9 downloaded.                                                                                                                                                  [ok]
Project entity contains 2 modules: entity, entity_token.
entity-7.x-1.6 downloaded.                                                                                                                                                [ok]
Project entityreference contains 2 modules: entityreference_behavior_example, entityreference.
entityreference-7.x-1.1 downloaded.                                                                                                                                       [ok]
entityreference_view_widget-7.x-2.0-rc6 downloaded.                                                                                                                       [ok]
entityreference_view_widget patched with entityreference_view_widget_suffix-2524296-2.patch.                                                                              [ok]
Generated PATCHES.txt file for entityreference_view_widget                                                                                                                [ok]
exif_orientation-7.x-1.0 downloaded.                                                                                                                                      [ok]
features-7.x-2.7 downloaded.                                                                                                                                              [ok]
field_collection-7.x-1.0-beta9 downloaded.                                                                                                                                [ok]
filefield_paths-7.x-1.0-rc1 downloaded.                                                                                                                                   [ok]
fraction-7.x-1.2 downloaded.                                                                                                                                              [ok]
geocoder-7.x-1.2 downloaded.                                                                                                                                              [ok]
geocoder patched with geocoder_multivalue_filefields-2352887-1.patch.                                                                                                     [ok]
geocoder patched with geocoder_kmz-2352931-2.patch.                                                                                                                       [ok]
Generated PATCHES.txt file for geocoder                                                                                                                                   [ok]
Project geofield contains 2 modules: geofield_map, geofield.
geofield-7.x-2.3 downloaded.                                                                                                                                              [ok]
geofield patched with geofield-delete_feature_fix-1350320-20.patch.                                                                                                       [ok]
Generated PATCHES.txt file for geofield                                                                                                                                   [ok]
geophp-7.x-1.7 downloaded.                                                                                                                                                [ok]
jquery_update-7.x-3.0-alpha3 downloaded.                                                                                                                                  [ok]
libraries-7.x-2.2 downloaded.                                                                                                                                             [ok]
libraries_cdn-7.x-1.7 downloaded.                                                                                                                                         [ok]
Project log contains 2 modules: log_plan, log.
log-7.x-1.0 downloaded.                                                                                                                                                   [ok]
Project logintoboggan contains 4 modules: logintoboggan_variable, logintoboggan_rules, logintoboggan_content_access_integration, logintoboggan.
logintoboggan-7.x-1.5 downloaded.                                                                                                                                         [ok]
navbar-7.x-1.6 downloaded.                                                                                                                                                [ok]
openlayers cloned from http://git.drupal.org/project/openlayers.git.                                                                                                      [ok]
Checked out revision deee17fd3bf605a273f2bfacca40b84aa1993c65.                                                                                                            [ok]
openlayers patched with openlayers_googlemaps_postbuild-2538168-5.patch.                                                                                                  [ok]
openlayers patched with openlayers_base_layer_mechanism-2543130-4.patch.                                                                                                  [ok]
openlayers patched with openlayers_google_maps_tilt_0-2573005-1.patch.                                                                                                    [ok]
Generated PATCHES.txt file for openlayers                                                                                                                                 [ok]
date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case[warning]
you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but
please set date.timezone to select your timezone. pm.drush.inc:2212
openlayers_geolocate_button-7.x-3.1 downloaded.                                                                                                                           [ok]
Project panels contains 5 modules: panels_node, panels_mini, panels_ipe, i18n_panels, panels.
panels-7.x-3.5 downloaded.                                                                                                                                                [ok]
pathauto-7.x-1.3 downloaded.                                                                                                                                              [ok]
pathauto_entity-7.x-1.0 downloaded.                                                                                                                                       [ok]
registry_autoload-7.x-1.3 downloaded.                                                                                                                                     [ok]
Project restws contains 2 modules: restws_basic_auth, restws.
restws-7.x-2.4 downloaded.                                                                                                                                                [ok]
role_delegation-7.x-1.1 downloaded.                                                                                                                                       [ok]
Project service_container contains 4 modules: service_container_block, service_container_symfony, service_container_annotation_discovery, service_container.
service_container-7.x-1.0-beta5 downloaded.                                                                                                                               [ok]
strongarm-7.x-2.0 downloaded.                                                                                                                                             [ok]
token-7.x-1.6 downloaded.                                                                                                                                                 [ok]
Project views contains 2 modules: views, views_ui.
views-7.x-3.11 downloaded.                                                                                                                                                [ok]
views patched with views_with_exposed-1809958-28.patch.                                                                                                                   [ok]
Generated PATCHES.txt file for views                                                                                                                                      [ok]
Project views_bulk_operations contains 2 modules: actions_permissions, views_bulk_operations.
views_bulk_operations-7.x-3.3 downloaded.                                                                                                                                 [ok]
views_data_export-7.x-3.0-beta8 downloaded.                                                                                                                               [ok]
views_geojson-7.x-1.0-beta2 downloaded.                                                                                                                                   [ok]
views_geojson patched with views_geojson_relative_source_url-2543622-1.patch.                                                                                             [ok]
Generated PATCHES.txt file for views_geojson                                                                                                                              [ok]
views_tree-7.x-2.0 downloaded.                                                                                                                                            [ok]
backup_migrate-7.x-3.1 downloaded.                                                                                                                                        [ok]
Project devel contains 3 modules: devel_generate, devel, devel_node_access.
devel-7.x-1.5 downloaded.                                                                                                                                                 [ok]
diff-7.x-3.2 downloaded.                                                                                                                                                  [ok]
module_filter-7.x-2.0 downloaded.                                                                                                                                         [ok]
farm_access-7.x-1.0 downloaded.                                                                                                                                           [ok]
farm_admin-7.x-1.0-beta6 downloaded.                                                                                                                                      [ok]
farm_area-7.x-1.0-beta6 downloaded.                                                                                                                                       [ok]
farm_asset-7.x-1.0-beta6 downloaded.                                                                                                                                      [ok]
farm_crop-7.x-1.0-beta6 downloaded.                                                                                                                                       [ok]
farm_equipment-7.x-1.0-beta6 downloaded.                                                                                                                                  [ok]
farm_fields-7.x-1.0-beta1 downloaded.                                                                                                                                     [ok]
Project farm_livestock contains 2 modules: farm_livestock_eggs, farm_livestock.
farm_livestock-7.x-1.0-beta6 downloaded.                                                                                                                                  [ok]
farm_log-7.x-1.0-beta6 downloaded.                                                                                                                                        [ok]
farm_map-7.x-1.0-beta6 downloaded.                                                                                                                                        [ok]
farm_mapknitter-7.x-1.1 downloaded.                                                                                                                                       [ok]
farm_sensor-7.x-1.0-beta3 downloaded.                                                                                                                                     [ok]
Project farm_soil contains 2 modules: farm_soil_test, farm_soil.
farm_soil-7.x-1.0-beta6 downloaded.                                                                                                                                       [ok]
farm_taxonomy-7.x-1.0-beta4 downloaded.                                                                                                                                   [ok]
bootstrap-7.x-3.1-beta3 downloaded.                                                                                                                                       [ok]
bootstrap patched with bootstrap_panel_element_id-2468625-7.patch.                                                                                                        [ok]
bootstrap patched with bootstrap_fluid_container_default-2556603-1.patch.                                                                                                 [ok]
Generated PATCHES.txt file for bootstrap                                                                                                                                  [ok]
farm_theme-7.x-1.0-beta6 downloaded.                                                                                                                                      [ok]
backbone downloaded from http://github.com/jashkenas/backbone/archive/1.1.2.zip.                                                                                          [ok]
modernizr downloaded from http://github.com/Modernizr/Modernizr/archive/v2.8.3.zip.                                                                                       [ok]
underscore downloaded from http://github.com/jashkenas/underscore/archive/1.7.0.zip.                                                                                      [ok]
You are about to create a /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/sites/default/settings.php file and CREATE the 'Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/quick-drupal-20151024182516.sqlite' database. Do you want to continue? (y/n): y
Starting Drupal installation. This takes a while. Consider using the --notify global option.                                                                              [ok]
exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1 there is already an index named log_type' in                                                     [error]
/Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/sqlite/database.inc:238
Stack trace:
#0 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/sqlite/database.inc(238): PDO->prepare('CREATE TABLE lo...', Array)
#1 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/sqlite/database.inc(456): DatabaseConnection_sqlite->PDOPrepare('CREATE
TABLE lo...')
#2 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/prefetch.inc(163): DatabaseStatement_sqlite->getStatement('CREATE TABLE
lo...', Array)
#3 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/sqlite/database.inc(461): DatabaseStatementPrefetch->execute(Array, Array)
#4 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/database.inc(683): DatabaseStatement_sqlite->execute(Array, Array)
#5 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/schema.inc(664): DatabaseConnection->query('CREATE TABLE {l...')
#6 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/database/database.inc(2720): DatabaseSchema->createTable('log_type', Array)
#7 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/common.inc(7064): db_create_table('log_type', Array)
#8 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/module.inc(462): drupal_install_schema('log')
#9 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/install.core.inc(1602): module_enable(Array, false)
#10 [internal function]: _install_module_batch('log', 'Log', Array)
#11 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/batch.inc(284): call_user_func_array('_install_module...', Array)
#12 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/form.inc(4704): _batch_process()
#13 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/install.core.inc(444): batch_process('install.php?pro...', 'http://default/...')
#14 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/install.core.inc(339): install_run_task(Array, Array)
#15 /Users/rjsteinert/Desktop/farmos/farm/quick-drupal-20151024182516/drupal/includes/install.core.inc(77): install_run_tasks(Array)
#16 /Users/rjsteinert/.composer/vendor/drush/drush/includes/drush.inc(720): install_drupal(Array)
#17 /Users/rjsteinert/.composer/vendor/drush/drush/includes/drush.inc(706): drush_call_user_func_array('install_drupal', Array)
#18 /Users/rjsteinert/.composer/vendor/drush/drush/commands/core/drupal/site_install_7.inc(80): drush_op('install_drupal', Array)
#19 /Users/rjsteinert/.composer/vendor/drush/drush/commands/core/site_install.drush.inc(289): drush_core_site_install_version(NULL, Array)
#20 [internal function]: drush_core_site_install(NULL)
#21 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(364): call_user_func_array('drush_core_site...', Array)
#22 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(215): _drush_invoke_hooks(Array, Array)
#23 [internal function]: drush_command(NULL)
#24 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(183): call_user_func_array('drush_command', Array)
#25 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(48): drush_dispatch(Array, Array)
#26 /Users/rjsteinert/.composer/vendor/drush/drush/commands/core/core.drush.inc(975): drush_invoke('site-install', Array)
#27 [internal function]: drush_core_quick_drupal()
#28 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(364): call_user_func_array('drush_core_quic...', Array)
#29 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(215): _drush_invoke_hooks(Array, Array)
#30 [internal function]: drush_command()
#31 /Users/rjsteinert/.composer/vendor/drush/drush/includes/command.inc(183): call_user_func_array('drush_command', Array)
#32 /Users/rjsteinert/.composer/vendor/drush/drush/lib/Drush/Boot/BaseBoot.php(62): drush_dispatch(Array)
#33 /Users/rjsteinert/.composer/vendor/drush/drush/drush.php(70): Drush\Boot\BaseBoot->bootstrap_and_dispatch()
#34 /Users/rjsteinert/.composer/vendor/drush/drush/drush.php(11): drush_main()
#35 {main}
Drupal core install failed.

Run on Rasperry Pi via Docker

I can get docker and docker compose installed but then when I run
sudo docker-compose up
I get

Creating network "farmos_default" with the default driver
Pulling db (mariadb:latest)...
latest: Pulling from library/mariadb
ERROR: no matching manifest for linux/arm in the manifest list entries

Steps to recreate

1. Install docker withcurl -sSL https://get.docker.com | sh from https://www.raspberrypi.org/blog/docker-comes-to-raspberry-pi/#
2. Install docker compose following https://www.berthon.eu/2017/getting-docker-compose-on-raspberry-pi-arm-the-easy-way/ with a few modifications

git clone https://github.com/docker/compose.git
cd compose
docker build -t docker-compose:armhf -f Dockerfile.armhf .
docker run --rm --entrypoint="script/build/linux-entrypoint" -v $(pwd)/dist:/code/dist -v $(pwd)/.git:/code/.git "docker-compose:armhf"
sudo cp dist/docker-compose-Linux-armv7l /usr/local/bin/docker-compose
sudo chown root:root /usr/local/bin/docker-compose
sudo chmod 0755 /usr/local/bin/docker-compose

Note: step 2 takes a long time (maybe 2 hours)

farmOS + PostGIS

Drupal's database abstraction layer supports PostgreSQL databases. Using PostgreSQL with farmOS would give us the ability to leverage PostGIS, which "is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL."

unable to display a Google Maps element

Upon a fresh install i received this error:

This page was unable to display a Google Maps element. Please contact the site administrator. If you are the administrator of this site, please check the JavaScript console or check the following page for troubleshooting: http://g.co/mapsJSApiErrors

I'm running:
farmOS 7.x-1.0-beta12

After i click OK at the bottom of the page i see:

"You are not authorized to access this page."

I read that the access denied error might be related to my sessions table being corrupted as well as possibly my cookies and cache needing to be cleared. I cleared my browser as well as optimized that sessions table and they didn't work.

Display acerage and relationships

Basic profile information should be displayed along with area maps:
Acreage
Parent and children areas
Soil types/slopes

A north arrow should also be added to map

Docker

The farmOS 7.x-1.x branch has a Dockerfile for building a Docker image: https://github.com/farmOS/farmOS/blob/7.x-1.x/Dockerfile

And we have a "docker" branch for figuring out some of the next steps: https://github.com/farmOS/farmOS/compare/docker

We also now have an official automated build on Docker Hub: https://hub.docker.com/r/farmos/farmos/

However, there are still some kinks to work out... I'm creating this issue to create a central place for discussion of those. Let's focus all new general discussion here, and from this we can maybe spin up some pull requests (if necessary).

Here are some previous (closed) discussions for reference and context:

#6
#10
#11
#13

Here are some related issues and PRs that are still open for discussion:

#14
#12

Link to official website from this repo's description?

Some articles like this one link directly to this repo. Inevitably, some non Github oriented people will land here, even some nice pictures in the README would help push them along.

Add Drush registry_rebuild to Docker container

Sometimes it is necessary to rebuild the Drupal class registry, and the easiest way to do that is with the Drush registry_rebuild project: https://www.drupal.org/project/registry_rebuild

Until we add this to the Docker image, it can be installed manually with the following command

sudo docker exec -it [www-container-name] drush -r /var/html/www @none dl registry_rebuild

Documentation, wiki, farmOS.org, etc

Starting this issue as a place to discuss documentation efforts...

Docker hub build error

Docker hub builds are currently failing with the following error:

Build failed: The command '/bin/sh -c apt-get update && apt-get install -y bzip2 git php5-geos phpunit unzip' returned a non-zero code: 100

Example: https://hub.docker.com/r/farmos/farmos/builds/bpleynmdmn8naaz2kx59unj/

Reports

Here are some ideas for reports I received today:

• an organic certification report.
• harvest record summary
• time (labor) per activity category e.g. how much time spent weeding, harvesting, feeding/watering animals etc
• a report that showed soil test results for a plot year over year matched with the amendments that were applied to that plot.
• a compost management report e.g. materials added, turning dates, temperature log, finish date
• field/bed history i.e. crops planted, management practices, amendments on each bed

Let's use this issue to collect more ideas, and then create specific feature requests in drupal.org/project/issues/farm

Error Load Module

What is the correct process for loading the Finland map module?
I uploaded the map through the web page but it gives an error. The original map disappears after uploading this module.
I'm testing this module, because I'll change it to load my own map.
Thanks!

Farm_Mushroom - unable to add new Mushroom Substrate record

PHP 5.5.5, Apache, FreeBSD, MySQL. FarmOS installed from Drupal pre-packaged distribution, farm_mushroom added from github.
After installation I able to add Substrate Type and Mushroom Species recrords. But when I try to add Mushroom Substrate - I can see only Location and Asset status fields.

When I try to fill it and Save - error displayed that I have to specify Name, Mushroom Species and Substrate type

ICT-AGRI call (EU)

It is quite a bit late for this call, and I do not know, if you have European partners, developers or organisations, but there is this funding from the European Union:
http://ict-agri.eu/node/37243

If there are Euopean partners, they might find consortia, partners or open proposals, e.g. here:
http://ict-agri.eu/groups/public_groups/37214
http://ict-agri.eu/node/14028

Add openStreetMaps layer(s)

If openStreetmaps could be used additionally or instead of GoogleMaps this could also help to use it as an airGapped-non-internet appliance, as described in #37

I am sure, it's possible and encouraged allowed to download and use the data from openStreetMaps locally.

I do not know how googleMaps offers the layer compared to OSM... and what's needed to offer them also the same way...

but it's an option possibly

Drush make adds stuff to .info files

Per @kadaan in IRC:

It seems as if drush is modifying the farm modules and adding ; Information added by drush on 2016-06-08\nversion = "7.x-1.2+0-dev"\nproject = "farm_access"\ndatestamp = "1465413099" to all the farm_*.info files. This make it a little bit more of a pain to work with these git repos

I noticed this too. It results in all the Git repos having outstanding changes, which is annoying.

I did a bit of digging and found this: drush-ops/drush#1326

Running drush make --help shows that there are two options:

 --no-gitinfofile                          Do not modify .info files when cloning from Git.                    
 --no-gitprojectinfo                       Do not inject project info into .info files when cloning from Git.

I'm not really sure what the difference is - maybe the first one is more comprehensive? Or maybe we need both?

I will try the --no-gitinfofile one first, and see what happens.

Log date widget limits to 3 years ago

A vineyard may have planted their grapes 50 years ago, but currently the widget used for log dates only allows you to select 3 years back. The database can support any date, so this is just a UI issue.

Google Map API problem

This is a crosspost from Drupal.org 2841845 (Not sure on better spot to post).

Installed FarmOS locally on OSX with MAMP with no issues with the map loading. (No API key needed)

Installed on a shared hosting account today. No issues with the other site functions, map just won't load. I've created the API key and saved it in the appropriate spot in the admin panel in Drupal. (It's a direct copy/paste so it is entered right). I've tried both with and without a referral site listed in the API developers panel in Google. Tried it with both domain name and IP address for the referral. After each change, I've cleared the Drupal cache and browser cache; no change.

In the console, I get three errors:

"Google Maps API error: MissingKeyMapError https://developers.google.com/maps/documentation/javascript/error-messag..." js:37:391
_.hb https://maps.googleapis.com/maps/api/js:37:391
Rm/this.f _.qz Am/c https://maps.googleapis.com/maps-api-v3/api/js/25/15/common.js:45:402
https://maps.googleapis.com/maps/api/js/AuthenticationService.Authentica...
"Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messag..." util.js:210:12
"Google Maps API warning: RetiredVersion https://developers.google.com/maps/documentation/javascript/error-messag..." util.js:210:12

I've spent probably 3 hours trying to fix this and am out of ideas. Any help would be appreciated.

Possible to lose sites folder during Docker rebuild

I discovered a potential issue with the way that the docker-entrypoint.sh script works that can cause the /var/www/html/sites folder to be lost permanently.

When the container is destroyed and rebuilt, the docker-entrypoint.sh script will detect whether or not /var/www/html/sites exists or not. If it does, it will move it up one directory to /var/www temporarily. Then it will build the farmOS codebase, and afterwards it moves the sites directory back.

When the sites directory is moved, it is essentially moved OUT of the volume and into the container. This is bad. This means that if the docker-entrypoint.sh script ends before it gets to the part that moves the sites folder back, the sites folder could be left outside of the volume. Then, if you destroy the container, it's lost.

This happened to me because I did Ctrl+C during the process of running drush make (I wanted to change something and run it again). Then, of course, I destroyed the container and recreated it so that I could rerun the drush make part. And when it finished, I was left with a clean slate install. :-(

Change Docker volume mount from /var/www/html to /var/www/html/sites (?)

Question: I'm going to put this up for consideration (and to help myself think it through by writing it out): should we change the default Docker image behavior to mount /var/www/html/sites as a volume, instead of the entire /var/www/html directory?

Background: Currently, the Dockerfile mounts the entire /var/www/html directory as a volume, which means that the farmOS codebase itself needs to be built AFTER the container starts (we do this via docker-entrypoint.sh). This is because when a directory is volume mounted into a Docker container from the host, it replaces the directory in the container, and therefore starts out as empty. So if we build the farmOS codebase in /var/www/html within the container, and then mounted that directory as a volume, it would be empty and the build would have been pointless.

However, this also means that the farmOS codebase cannot be updated simply by pulling a new version of the Docker image. It also needs to be rebuilt in the volume. We have some clever logic (aka extra complexity) in docker-entrypoint.sh that takes care of this automatically by detecting the installed farmOS version using Drush, and automatically rebuilding if the version changes.

Additionally, the docker-entrypoint.sh has two pathways to build the farmOS codebase: 1) download a packaged release for a specific version, or 2) build the latest development version with Drush. The approach it takes is toggled with the FARMOS_DEV boolean environment variable.

I don't love all of the complexity required for these things, but they got the job done for an initial Docker integration (and yes, I learned a lot about Docker through the process). For more historical perspective on these details, see the original issue thread that added Docker integration for farmOS: #15

Proposal: So now I am thinking about ways to simplify. If we did build the farmOS directly in the container, and mounted /var/www/html/sites as a volume instead of /var/www/html, then we could remove a lot of the complex logic in docker-entrypoint.sh.

This alone would not solve the tagged release vs development version use-case, however. For that, maybe it would make sense to offer two different Dockerfiles (and two different docker-compose.yml files).

Something to think about...

FarmOS Offline Mode

Hello! First, thank you for creating and maintaining this project.

I was wondering if it would be possible to have an "offline mode" for FarmOS. That is, allow FarmOS to work without an internet connection.

For example my family lives out where there is no real internet connection to speak of. However, I have a local network that covers the house, which I plan to extend out to the main fields as well, with a personal web server. I have FarmOS running and can access it with all local computers and tablets, but each page load is very slow and takes up the precious little bandwidth I do have because it has to fetch external fonts, stylesheets, and scripts.

I would like to use FarmOS to track information, but the requirement for an internet connection makes FarmOS almost useless to me. :( I'm mostly looking for instructions on how to remove**, or better yet host locally**, all the parts requiring an internet connection. Though it would be really nice if it was an option/step in the installation process.

Thank You!

Change language

Hi!
I'm thinking about translation on Russian. What is the best way to do it?

Install PECL Uploadprogress in Docker container

PECL Uploadprogress should be installed since all the file fields in farmOS use the uploadprogress widget.

Options for standardizing on vocabularies for interoperability when publishing a Web API

It looks like the UN has done some work on creating an ontology for Agriculture, it's an ontology called Agrovoc (read their about page). The UN has also sponsored some work in Drupal to get Agrovoc into Drupal. It's not entirely clear if that vocab is a clear fit for Drupal Farm, it will take some more digging. Here's what I've found so far.

• AgriDrupal installation profile
  • doesn't look like this was ever finished, not in the Installation Profiles list on Drupal.org
  • about page on the UN ag site
  • AgriDrupal demo site
  • An announcement from 2013 that AgriDrupal is released but the download link is broken
  • An announcement that a new website is using AgriDrupal from 2014
• UN sponsored Agrovoc module which has some commits from June 2014
• UN sponsored Agrovocfield module

Add mysql-client in Docker www container for Drush

Drush is unable to connect to a MariaDB database without mariadb-client installed.

To fix manually, install the mariadb-client package in the www container after it is up and running:

sudo docker exec -it [container name] bash
apt-get install mariadb-client

This started happening when we switched to using MariaDB for the database container instead of MySQL. Notably we didn't need to install mysql-client when we were using MySQL. I wonder if that is packaged automatically in the Drupal base image, or if it is added as a dependency automatically for something else.

Commas in Area Asset names cause problems

I've now created (twice!) area names with commas in them, and ended up with two areas, one with the name before the comma, and one with a name after the comma.

Is there any way to ignore the comma when working with areas?

drush make Fails

Hi,
$drush make build-farm.make farm

The 'core' attribute is required [error]
You need to specify an API version of two in your makefile: [warning]
api = 2
Beginning to build build-farm.make. [ok]
No core project specified. [error]
Drush Make failed to download all projects. See the log above for the[error]
specific errors.

Best wishes

Confirm that Docker users can upgrade from 7.x-1.x to tagged releases

People have started using the farmOS Docker image, which is currently configured to build the 7.x-1.x development branch of farmOS - not the latest stable tagged release (7.x-1.0-beta12). The Docker image was added since the latest tagged release, so a tagged release image will not be available on Docker Hub until 7.x-1.0-beta13 is released.

At that point, I would like to recommend that anyone using Docker switch to the beta13 tagged image, to ensure that it is stable and that all the included modules work together as intended.

However, I want to double check that moving from a branch image (ie: 7.x-1.x) to a tag image (ie: 7.x-1.0-beta13) will not break anything for Docker users.

If you are using Docker, please feel free to follow this thread. I will investigate and post any details that you need to know.

Docker container can't send emails

Currently emails can't be sent, and on install the following error shows: Unable to send e-mail. Contact the site administrator if the problem persists.

Docker volume ownership

When using Docker and Docker Compose to set up a local development environment (see http://farmos.org/development/docker), the Docker container's /var/www/html directory is mounted as a volume in the host. This allows the developer to modify the farmOS codebase directly from the host, so they can use an IDE like PHPStorm, for example.

However, by default, Docker runs as root, so the files mounted in the volume are owned by root. This makes it difficult to develop.

Let's use this issue to discuss potential approaches and considerations.

Docker image tag: 'latest'

The farmOS Docker image does not currently have a 'latest' tag on Docker hub. When the next tagged release of farmOS is done, let's create a 'latest' tag that points to the new stable tagged release, and continues to moving forward.

Seed management

This is a feature request. I don't know if it could be done as a new module or as a modification of some existing module. I would like to manage seeds in a similar way as I can manage Plantings/Varieties.

Suggested workflow:
I begin registering my seed stock: Some carrots, some Belstar F1 Organic Broccoli, some local variety of lettuce, etc., each one with historical stock registering quantities, different units (grams, units, ...), sell-by-date, etc.
Then, when I create a new Planting asset, I can select the seed used and the units consumed.
And finally, I can Harvest some planting as seeds, creating new historical stock for the seed or creating a new Hybrid Seed.

What does the communitie think about this feature? Could be more people interested?

I have some skills in PHP but I'm not a Drupal developer, so I can help but only a little bit.
Thank you farmOS team!

nested make file in openlayer-7.x-2.x-beta9 has broken uri, causes `drush make build-farm.make` to fail

Kind of a sorry state of affairs for us and the Open Layers Drupal module. See discussion here. Setting the dependency verson to 2.x-dev temporarily fixes the problem but I think having dev dependency versions can create unpredictable results for drupal profiles. We may want to maintain our own fork of the Open Layers module until the maintainer of the Open Layers module decides to drop the nested make file.

PHP 7 + GEOS

See https://www.drupal.org/project/geophp/issues/1754138#comment-12225492

Planning vs Record keeping?

I'm having a hard time getting my head around what farmOS is meant to do. I watched the NOFA video and it seems like it's focused on collecting info from ad hoc sources (sensors, etc) and also tracking activities as they happen or after they've happened. Is that correct?

I ask because I'm in the middle of redoing my old CropPlanning Software desktop-based Java project in PHP/Laravel as a web-based offering. The idea behind that is to help with stuff like: "I need to harvest 200# of cabbage on 8/28. How much seed do I need to order and when I do need to plant it? Oh, and how many trays will that be?", etc.

Does farmOS offer planning support of this kind? I hate reinventing the wheel!

Thanks!

PS - sorry to open an issue for this ... I couldn't find an email address to send to.

Issues with Docker db images on Windows 10 Home

Steve tried to get farmOS up and running on Windows 10 Home using Docker Toolbox, and ran into an issue with the MariaDB image:

Creating farmos_db_1  ... done
Creating farmos_db_1  ...
Creating farmos_www_1 ... done
Attaching to farmos_db_1, farmos_www_1
db_1   | Initializing database
www_1  | farmOS not detected. Building...
db_1   | 2018-02-28  3:40:37 140158690969472 [Warning] InnoDB: Failed to set O_DIRECT on file./ibdata1;CREATE: Invalid argument, ccontinuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662.
db_1   | 2018-02-28  3:40:44 140158690969472 [ERROR] InnoDB: Operating system error number 22 in a file operation.
db_1   | 2018-02-28  3:40:44 140158690969472 [ERROR] InnoDB: Error number 22 means 'Invalid argument'
db_1   | 2018-02-28  3:40:44 140158690969472 [ERROR] InnoDB: File ./ib_logfile101: 'aio write' returned OS error 222. Cannot continue operation
db_1   | 180228  3:40:44 [ERROR] mysqld got signal 6 ;
db_1   | This could be because you hit a bug. It is also possible that this binary
db_1   | or one of the libraries it was linked against is corrupt, improperly built,
db_1   | or misconfigured. This error can also be caused by malfunctioning hardware.
db_1   |
db_1   | To report this bug, see https://mariadb.com/kb/en/reporting-bugs
db_1   |
db_1   | We will try our best to scrape up some info that will hopefully help
db_1   | diagnose the problem, but since we have already crashed,
db_1   | something is definitely wrong and this may fail.
db_1   |
db_1   | Server version: 10.2.13-MariaDB-10.2.13+maria~jessie
db_1   | key_buffer_size=134217728
db_1   | read_buffer_size=2097152
db_1   | max_used_connections=0
db_1   | max_threads=102
db_1   | thread_count=0
db_1   | It is possible that mysqld could use up to
db_1   | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759916 K  bytes of memory
db_1   | Hope that's ok; if not, decrease some variables in the equation.
db_1   |
db_1   | Thread pointer: 0x0
db_1   | Attempting backtrace. You can use the following information to find out
db_1   | where mysqld died. If you see no messages after this, something went
db_1   | terribly wrong...
db_1   | stack_bottom = 0x0 thread_stack 0x49000
db_1   | /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x555829812b3e]
db_1   | /usr/sbin/mysqld(handle_fatal_signal+0x345)[0x55582928f3e5]
db_1   | /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f793cbad890]
db_1   | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f793af38067]
db_1   | /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f793af39448]
db_1   | /usr/sbin/mysqld(+0x888456)[0x555829490456]
db_1   | /usr/sbin/mysqld(+0x88ee46)[0x555829496e46]
db_1   | /usr/sbin/mysqld(+0xa2ff4b)[0x555829637f4b]
db_1   | /usr/sbin/mysqld(+0x86c12f)[0x55582947412f]
db_1   | /usr/sbin/mysqld(+0x86d022)[0x555829475022]
db_1   | /usr/sbin/mysqld(+0x86d89d)[0x55582947589d]
db_1   | /usr/sbin/mysqld(+0x87370a)[0x55582947b70a]
db_1   | /usr/sbin/mysqld(+0x41fb8a)[0x555829027b8a]
db_1   | /usr/sbin/mysqld(+0x92b06d)[0x55582953306d]
db_1   | /usr/sbin/mysqld(+0x80de69)[0x555829415e69]
db_1   | /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x555829291734]
db_1   | /usr/sbin/mysqld(+0x4ee665)[0x5558290f6665]
db_1   | /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x8aa)[0x5558290f7d7a]
db_1   | /usr/sbin/mysqld(+0x44113e)[0x55582904913e]
db_1   | /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x65e)[0x55582904e6be]
db_1   | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f793af24b45]
db_1   | /usr/sbin/mysqld(+0x43925d)[0x55582904125d]
db_1   | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
db_1   | information that should help you find out what is causing the crash.
db_1   | Aborted
db_1   |
db_1   | Installation of system tables failed!  Examine the logs in
db_1   | /var/lib/mysql/ for more information.
db_1   |
db_1   | The problem could be conflicting information in an external
db_1   | my.cnf files. You can ignore these by doing:
db_1   |
db_1   |     shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf
db_1   |
db_1   | You can also try to start the mysqld daemon with:
db_1   |
db_1   |     shell> /usr/sbin/mysqld --skip-grant-tables --general-log &
db_1   |
db_1   | and use the command line tool /usr/bin/mysql
db_1   | to connect to the mysql database and look at the grant tables:
db_1   |
db_1   |     shell> /usr/bin/mysql -u root mysql
db_1   |     mysql> show tables;
db_1   |
db_1   | Try 'mysqld --help' if you have problems with paths. Using
db_1   | --general-log gives you a log in /var/lib/mysql/ that may be helpful.
db_1   |
db_1   | The latest information about mysql_install_db is available at
db_1   | https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
db_1   | You can find the latest source at https://downloads.mariadb.org and
db_1   | the maria-discuss email list at https://launchpad.net/~maria-discuss
db_1   |
db_1   | Please check all of the above before submitting a bug report
db_1   | at http://mariadb.org/jira
db_1   |
www_1  | Cloning into '/var/farmOS'...
www_1  | Beginning to build /var/farmOS/build-farm.make.                             [ok]
farmos_db_1 exited with code 1

It appears that this is the important line:

db_1 | 2018-02-28 3:40:37 140158690969472 [Warning] InnoDB: Failed to set O_DIRECT on file./ibdata1;CREATE: Invalid argument, ccontinuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662.

Searching for that brought me to: MariaDB/mariadb-docker#38

According to that issue, it sounds like there's an issue with the MariaDB 10.1 issue.

Install Profile Error

Going through the install on 1and1 the database got created ok, but then I got an error related to a Drupal service container not found. How do I go about making this container available. I've attached the error messages. I ftp'd the files I got from the Drupal site rather than using the 1and1 install because they are on v8, but it seems that the v7 install from the Drupal site should have worked. Thanks for your help; I'm excited about using this software next season.
install_profile_errors.docx

Geolocate button not working

When I try to add an area and I hit the geolocate button nothing happens.

Initial farm setup - making it easier to define areas

For background: My orchard is relatively new so Google Earth imagery does not reflect the current planted state. As such, I know the sizes of my planted areas (row lengths, space between rows) and so size is the easiest way to go about drawing it on the map. Here are some suggestions:

• Show measurements of the lines as they're being drawn (ft, yds, etc)
• Show measurements of different sides of the polygon as they're completed (ft, yds)
• Show area measurements as the shape is being completed (sq ft, acres)
• Allow the user to select a custom color for their area
• Label the Area map with the Area names (could be done with layers?) to allow new employees to see a sort of site map
• Allow the user to draw a Geometry of an Asset on creation
• Allow the user to lock the Geometry of an Asset so that it can't be moved (or mark it as a permanent planting perhaps)

Expose sensor data and config via REST API

It would be nice if it was possible to easily extract all data via the REST API.

Hiearchy Change URL doesnt work for subdirectory installation

If FarmOS is installed within a subdirectory, instead of being on a dedicated server, the Hierarchy Change URL navigates to http://domain/admin/structure/taxonomy/farm_areas when it should navigate to http://domain/subdirectory/admin/structure/taxonomy/farm_areas.

In the lower left of the attached screenshot, it shows that the change link navigates to "http://thepost/?q=admin/structure/taxonomy/farm_areas&destination=farm/areas" when it should navigate to (based on the URL in the browser) "http://thepost/farmosweb?q=admin/structure/taxonomy/farm_areas&destination=farm/areas".

Not sure which line is causing this problem. I've narrowed it down to lines 49 and 155. I believe that line is 155 that's the problem. Removing the leading slash (before admin) in the URL should fix this.

farmOS/modules/farm/farm_area/farm_area.views_default.inc

Line 49 in 4dc82b5

$handler->display->display_options['header']['area_text_custom']['content'] = '<h4>Hierarchy <small>' . l('(change)', 'admin/structure/taxonomy/farm_areas', array('query' => array('destination' => 'farm/areas'))) . '</small></h4>';

farmOS/modules/farm/farm_area/farm_area.views_default.inc

Line 155 in 4dc82b5

t('<h4>Hierarchy <small><a href="/admin/structure/taxonomy/farm_areas?destination=farm/areas">(change)</a></small></h4>'),

Areas not being displayed

Using containers from the docker-compose.yml on 7.x-1.x branch at commit 5073592.

When I marked out the areas as per the attached screenshot I figured I would see some different things. When I scroll in enough I can see the property as a grey box, but that is all. Is this the expected behavior

It shows up the same on a chrome book and via Chrome 58.0.3029.96

First is the overview of all

Second is a zoom on the paddocks. Top paddock, bottom paddock and orchard are all in the view. All boxes are selected in the layers menu except soil samples.

Docker Image

Is there a docker file for this?

Enable Docker tagged releases via docker-compose.yml

As stated in the farmOS Docker documentation: (http://farmos.org/development/docker/)

The docker-compose.yml file included with farmOS sets FARMOS_DEV to true by default, so it is intended only for development purposes at this time.

We could adopt a slight change to the "new release procedure" (farmOS/farmOS.org#16) that comments out this line of docker-compose.yml for the tagged releases. This would mean that you could checkout the release tag in the farmOS repo and run sudo docker-compose up, and you would actually end up with the tagged release codebase (which is what you would normally expect to happen).

I will test this out to make sure I'm not missing anything, but this seems like a logical next step.

If this happens, the Docker documentation should also be updated, and we should include instructions for building development vs tagged releases via Docker locally.

SQL Errors while installing via Docker Compose

I was trying to reinstall my development server with docker-compose and when I get to the install screen, I get this error after entering the db info:

Warning: PDO::__construct(): MySQL server has gone away in DatabaseConnection->__construct() (line 321 of /var/www/html/includes/database/database.inc).
Warning: PDO::__construct(): Error while reading greeting packet. PID=20 in DatabaseConnection->__construct() (line 321 of /var/www/html/includes/database/database.inc).
Resolve all issues below to continue the installation. For help configuring your database server, see the installation handbook, or contact your hosting provider.
Failed to connect to your database server. The server reports the following message: SQLSTATE[HY000] [2006] MySQL server has gone away.

This is similar to an error I encountered the first time I installed, which I believe was resolved by changing some permissions, though now I can't recall how.

System info: Running Ubuntu 16.04, and b/c I have some old, conflicting SQL/Apache instances that I haven't figured out how to kill, I've modified docker-compose.yml to:

db:
    ports:
        - '3307:3306'
www:
    ports:
        - '9090:80'

Those modifications were reflected in the info I gave to the installer.

Recommendation engine use-case brainstorm

In the last monthly call (and at other points in the past) we've discussed the potential for farmOS to make recommendations, based on other information it has stored already.

Some example use-cases that have come up:

• Cover crop recommendations based on previous crops planted, and/or future crop plans
• Warning if planting into manure that has not had enough time to compost
• Warning if a harvest is scheduled too soon after a spray was applied

Some that Wynand Britz sent me after the call:

1. Chemical database with recommendations and waiting periods for follow up crops
2. Field input database for synergy with all roll players for instance when pollinators are there not to use certain chemicals
3. Integrating Technology like rain sensors and thermostats to fields to track weather properly per land
4. Integrating the Pivots data to Farm OS for the farmers with irrigation.
5. (Missed this one sorry) Budget vs Actual on crops to show what chemicals have been used when and what is in storage still to be used for farmer and consultants to keep track of what is going on.
6. Input field for farm visits for consultants and farm workers where they can GPS plot with pictures problems they get. For instance if they find an area with blight in potatoes to GeoTag it with n picture for the others who have access to find it easily for follow ups.

Let's use this thread to brainstorm more potential use-cases for recommendations.

Unable to setup docker instance on mac

I am running mac os sierra. I followed all the steps mentioned in the documentation. Initially when starting the docker instance, i was facing issue where my sql instance was starting but web was failing.

With some help, we figured out that a default apache instance is running. I disabled apache and everything went fine. When i start my docker instance both web and mysql starts. I get ok for both on terminal.

But i can't see anything in browser. I did the network fix as well but nothing works.