Sync with farmstack-open repository

.gitbook.yaml

@@ -0,0 +1,5 @@
+root: ./docs/
+
+structure:
+  readme: ../README.md
+  summary: SUMMARY.md

.github/workflows/example_uc.yml

@@ -0,0 +1,28 @@
+name: UC Test Case
+
+on:
+  push:
+    branches: [ main, mayank/new/github-actions ]
+  pull_request:
+    branches: [ main ]
+
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Running setup script
+        run: ./scripts/examples/run-uc.sh
+
+      - name: Wait for connector to come online
+        run: sleep 60
+
+      - name: Checking for data transfer
+        run: ./scripts/examples/checkData.sh
+
+      - name: Stopping containers
+        run: ./scripts/examples/stop-uc.sh

.github/workflows/self-managed-demo.yml

@@ -0,0 +1,19 @@
+name: Self Connector Setup
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      # - name: Running setup script
+        # run: python3 setup.py

.gitignore

@@ -105,4 +105,9 @@ dist
 # TernJS port file
 .tern-port
 
-.DS_Store
+.DS_Store
+
+venv/
+.venv/
+.setup_complete
+.idea

LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -1,27 +1,69 @@
-### What is FarmStack?
-FarmStack is a digital infrastructure that enables data collaboration between different entities. It does this by providing a means to:
-1. Share data directly to the relevant organization without the need of third party through p2p connector (peer to peer connector) 
-2. Empower the data provider to specify how data can or cannot be used by the receiver through data owner defined usage policies
-3. Enable organizations to make their data discoverable by publishing metadata (description of connectors and usage policies) and shareable through data interface containers
+# Introduction
+
+![](https://github.com/digitalgreenorg/farmstack-open/actions/workflows/example\_uc.yml/badge.svg)
+
+![](docs/.gitbook/assets/farmstack\_horizontal\_color\_transparent-bg.png)
+
+FarmStack is a reference implementation of an open and interoperable data sharing protocol in agriculture sector.
 
-### Why is FarmStack required?
 FarmStack is required because:
-*  Lack of trust on misuse or under utilization of data for centralized data repository
-*  Need to comply with evolving data policy and privacy safeguarding measures
 
-### Value generated by FarmStack
-* By combining specific datasets, better services or products can be created
-* Potential to unlock value of data that was previously considered not shareable
-* More the feedback from farmers is combined, more enriching the solution can be - giving rise to virtuous cycle
+* Relevant farmer profile including farmer activity not available
+* Lack of trust on misuse or under utilisation of data with a centralised data warehouse
+* Need to comply with evolving data policy and privacy safeguarding measures
+* Existing data integration tools lack the customisation
+
+## Quick start
+
+```bash
+git clone https://github.com/digitalgreenorg/farmstack-open.git
+cd farmstack-open
+python3 setup.py
+```
+
+In browser, open: [http://localhost:8000/](http://localhost:8000) and follow the instructions
+
+For more details see [local deployment](docs/deploying-farmstack/local-deployment.md).
+
+Requirements:
+
+* Python3.6+
+* Docker Desktop (for MacOS and Windows with wsl2).
+* Docker and Docker Compose for ubuntu
+
+## Deployment and Guides
+
+You can see FarmStack in action by [Setting up Video Library Connector](docs/deploying-farmstack/setting-up-video-library-connector.md) for fetching data from [Digital Green's Video Library](https://solutions.digitalgreen.org/videos/library).
+
+Or you can follow one of our step-by-step guide to setup your own connectors:
+
+* [Configuring a connector with CSV file](docs/operation-guides/creating-a-connector-with-csv.md) 
+* [Dockerizing applications to be compatible with FarmStack Connector](docs/operation-guides/dockerization/)
+* [Install a dockerized application with a connector](docs/operation-guides/install-a-nodejs-application-with-connector.md)
+
+## Features
+
+FarmStack enables network of data providers and consumers through a suite of products and functionalities:
+
+1. Share data directly without any third party through trusted **peer to peer (p2p) connector**.
+2. Empower the data provider to restrict usage of data through **usage policies**.
+3. Give control of data back to the farmers by managing consent using **data wallet**.
+4. Enable entities to create plugins to make their **data discoverable (description of data)**.
+
+FarmStack is the sum total of all the peer to peer connectors and associated usage policies.
+
+For more information visit [our website](https://www.farmstack.co) or [Confluence Page](https://digitalgreenorg.atlassian.net/wiki/spaces/FS/overview).
+
+## Contributing
+
+We would love your contribution to this project no matter big or small.
+
+To get started see our [contribution guide](docs/contributing-to-farmstack.md).
 
-### How does someone use FarmStack
+## Roadmap
 
-Business roles in FS can be viewed as layered operational spheres:
-* __FS Participants__ : These are stakeholders who are actually performing data exchange or providing some services for data exchange. This is mainly a data provider and data consumer
-* __FS Central/ Steward__ : This is a nodal agency/ consortium who will run farmstack in that geography/ jurisdiction. They will operate the gateways for the participants. Examples could be MoA or a global consortium.
-* __FS Core__: This is the technology stack that is maintained by DG and consortium based on IDS technology stack (Fraunhofer) which consists of the code repo under MIT/ Apache license. They will own the master services agreement - governance structure and the right to provision instance of FS central.
+@TODO - Add Roadmap
 
-#### Example:
-Consider the diagram, there are two instances of FS run by two independent central bodies in different jurisdictions. Let us say MoA of Country1 and Country2 run separate instances of FarmStack C1 and C2 which have participants P1… Pn who do data exchange between each other. By provisioning FS, C1 and C2 run FS on their server in addition to managing the organizations.
+## License
 
-<img src="FS-business sphere.png"  height="250">
+Farmstack is licensed under Apache License 2.0. See [LICENSE](https://github.com/digitalgreenorg/farmstack-open/tree/576aa2ca789cd6910b3aee1d7ebd9cce08d73cf6/LICENSE/README.md) file for licensing information

docs/SUMMARY.md

@@ -0,0 +1,22 @@
+# Table of contents
+
+* [Introduction](../README.md)
+* [Quick Start](quick-start/README.md)
+  * [Deploy Farmstack](quick-start/deploy-farmstack.md)
+  * [Removing farmstack](quick-start/removing-farmstack.md)
+* [Deploying Farmstack](deploying-farmstack/README.md)
+  * [Installing Prerequisites](deploying-farmstack/installing-prerequisites.md)
+  * [Setting up Self-Managed Connectors](deploying-farmstack/setting-up-self-managed-connectors.md)
+  * [Setting up Video Library Connector](deploying-farmstack/setting-up-video-library-connector.md)
+  * [Local Deployment](deploying-farmstack/local-deployment.md)
+  * [Deployment on AWS EC2](deploying-farmstack/aws-ec2.md)
+* [Guides](operation-guides/README.md)
+  * [Configuring a connector with CSV](operation-guides/creating-a-connector-with-csv.md)
+  * [Configuring a connector with JSON/Rest API](operation-guides/configuring-a-connector-with-json-rest-api.md)
+  * [Configuring a connector with Google Sheets](operation-guides/configuring-a-connector-with-google-sheets.md)
+  * [Dockerization](operation-guides/dockerization/README.md)
+    * [NodeJS](operation-guides/dockerization/dockerization-nodejs.md)
+    * [Django](operation-guides/dockerization/dockerization-django.md)
+    * [Flask](operation-guides/dockerization/dockerization-flask.md)
+  * [Install a dockerized application with connector](operation-guides/install-a-nodejs-application-with-connector.md)
+* [Contributing to FarmStack](contributing-to-farmstack.md)

docs/contributing-to-farmstack.md

@@ -0,0 +1,4 @@
+# Contributing to FarmStack
+
+Thank you for your interest in contributing to FarmStack, currently we are building our contribution guidelines. Meanwhile you can contact us on our [website](https://www.farmstack.co) and [confluence](https://digitalgreenorg.atlassian.net/wiki/spaces/FS/overview).
+

docs/deploying-farmstack/README.md

@@ -0,0 +1,2 @@
+# Deploying Farmstack
+

docs/deploying-farmstack/aws-ec2.md

@@ -0,0 +1,2 @@
+# Deployment on AWS EC2
+