{"id":19527745,"url":"https://github.com/jukbot/growth","last_synced_at":"2026-03-19T10:18:04.089Z","repository":{"id":47011995,"uuid":"89486649","full_name":"jukbot/growth","owner":"jukbot","description":"Smart Watering System","archived":false,"fork":false,"pushed_at":"2021-09-17T10:03:04.000Z","size":19279,"stargazers_count":1,"open_issues_count":1,"forks_count":0,"subscribers_count":0,"default_branch":"master","last_synced_at":"2025-11-20T03:06:46.641Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/jukbot.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2017-04-26T13:53:29.000Z","updated_at":"2023-03-09T00:25:53.000Z","dependencies_parsed_at":"2022-08-31T05:12:25.274Z","dependency_job_id":null,"html_url":"https://github.com/jukbot/growth","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/jukbot/growth","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jukbot%2Fgrowth","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jukbot%2Fgrowth/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jukbot%2Fgrowth/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jukbot%2Fgrowth/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/jukbot","download_url":"https://codeload.github.com/jukbot/growth/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jukbot%2Fgrowth/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29991835,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-02T01:47:34.672Z","status":"online","status_checked_at":"2026-03-02T02:00:07.342Z","response_time":60,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-11T01:16:16.859Z","updated_at":"2026-03-02T03:34:15.480Z","avatar_url":"https://github.com/jukbot.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Problem Statement\n\nIn the present, without well-managed watering system can cause many problems during watering plants in agricultural, for example, unsuitable amount of water due to types of plant, temperature, and moisture in the air. Thus, people sometimes waste water more or less than it should be, and the quality of product might not be good enough for the market.   \n\n\n# Background\n\nInefficient watering plant management may lead to an excessive or insufficient in using water. Getting unsuitable amount of water will also make less productivity of plant. Therefore, we need an efficient watering management system in order to know the suitable amount of water for specific types of plant due to various weather conditions.\n\n\n\n## Build Status\n\n\n\n## System Requirement\n\n### Operation System\n- Windows 10\n- MacOS 10.12\n- Ubuntu 14.04, 16.04\n- CentOS 7.2\n\n### Browsers\n- Google Chrome 59\n- Firefox 53\n- Microsoft Edge 15 (!!Unstable!!) \n\n## What is Polymer ?\n\nPolymer is a lightweight library built on top of the web standards-based [Web Components](http://webcomponents.org/) API's, and makes it easier to build your very own custom HTML elements. Creating reusable custom elements - and using elements built by others - can make building complex web applications easier and more efficient. By being based on the Web Components API's built in the browser (or [polyfilled](https://github.com/webcomponents/webcomponentsjs) where needed), Polymer elements are interoperable at the browser level, and can be used with other frameworks or libraries that work with modern browsers.\n\nAmong many ways to leverage custom elements, they can be particularly useful for building reusable UI components. Instead of continually re-building a specific navigation bar or button in different frameworks and for different projects, you can define this element once using Polymer, and then reuse it throughout your project or in any future project.\n\nPolymer provides a declarative syntax to easily create your own custom elements, using all standard web technologies - define the structure of the element with HTML, style it with CSS, and add interactions to the element with JavaScript.\n\nPolymer also provides optional two-way data-binding, meaning:\n\n1. When properties in the model for an element get updated, the element can update itself in response.\n2. When the element is updated internally, the changes can be propagated back to the model.\n\nPolymer is designed to be flexible, lightweight, and close to the web platform - the library doesn't invent complex new abstractions and magic, but uses the best features of the web platform in straightforward ways to simply sugar the creation of custom elements.\n\nIn addition to the Polymer library for building your own custom elements, the Polymer project includes a collection of [pre-built elements](https://elements.polymer-project.org) that you can  drop on a page and use immediately, or use as starting points for your own custom elements.\n\n\nThe PRPL pattern, in a nutshell:\n\n* **Push** components required for the initial route\n* **Render** initial route ASAP\n* **Pre-cache** components for remaining routes\n* **Lazy-load** and progressively upgrade next routes on-demand\n\n### Migrating from Polymer Starter Kit v1?\n\n[Check out our blog post that covers what's changed in PSK2 and how to migrate!](https://www.polymer-project.org/1.0/blog/2016-08-18-polymer-starter-kit-or-polymer-cli.html)\n\n### Setup\n\n##### Prerequisites\n\nNodeJS version \u003e= 6.x\n\n    https://nodejs.org/en/\n\nInstall [polymer-cli](https://github.com/Polymer/polymer-cli):\n\n    npm install -g polymer-cli\n\nInstall bower:\n\n    npm install -g bower\n\n\n### Start the development server\n\nThis command serves the app at `http://localhost:8080` and provides basic URL\nrouting for the app:\n\n    polymer serve --open\n\n\n### Build\n\nThis command performs HTML, CSS, and JS minification on the application\ndependencies, and generates a service-worker.js file with code to pre-cache the\ndependencies based on the entrypoint and fragments specified in `polymer.json`.\nThe minified files are output to the `build/unbundled` folder, and are suitable\nfor serving from a HTTP/2+Push compatible server.\n\nIn addition the command also creates a fallback `build/bundled` folder,\ngenerated using fragment bundling, suitable for serving from non\nH2/push-compatible servers or to clients that do not support H2/Push.\n\n    polymer build --add-service-worker\n\n### Preview the build\n\nThis command serves the minified version of the app at `http://localhost:8080`\nin an unbundled state, as it would be served by a push-compatible server:\n\n    polymer serve build/unbundled\n\nThis command serves the minified version of the app at `http://localhost:8080`\ngenerated using fragment bundling:\n\n    polymer serve build/bundled\n\n### Run tests\n\nThis command will run\n[Web Component Tester](https://github.com/Polymer/web-component-tester) against the\nbrowsers currently installed on your machine.\n\n    polymer test\n\n### Adding a new view\n\nYou can extend the app by adding more views that will be demand-loaded\ne.g. based on the route, or to progressively render non-critical sections\nof the application.  Each new demand-loaded fragment should be added to the\nlist of `fragments` in the included `polymer.json` file.  This will ensure\nthose components and their dependencies are added to the list of pre-cached\ncomponents (and will have bundles created in the fallback `bundled` build).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjukbot%2Fgrowth","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjukbot%2Fgrowth","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjukbot%2Fgrowth/lists"}