From bf6fb1e784c57b9614e99c8f23180a25e504b008 Mon Sep 17 00:00:00 2001 From: Aatman Vaidya Date: Thu, 22 Feb 2024 11:53:50 +0530 Subject: [PATCH] chore: deleting docker-compose-standalone and renaming privacy policy (#89) --- privacy_policy.md => PRIVACY_POLICY.md | 2 +- docker-compose-standalone.yml | 37 -------------------------- 2 files changed, 1 insertion(+), 38 deletions(-) rename privacy_policy.md => PRIVACY_POLICY.md (65%) delete mode 100644 docker-compose-standalone.yml diff --git a/privacy_policy.md b/PRIVACY_POLICY.md similarity index 65% rename from privacy_policy.md rename to PRIVACY_POLICY.md index 6e48ede5..56319c1c 100644 --- a/privacy_policy.md +++ b/PRIVACY_POLICY.md @@ -2,4 +2,4 @@ Feluda is a configurable engine that lets people plug-in different operators or libraries such as Google Cloud Vision API, ResNet, pHash. One can also add their own custom analysis tool as an operator to Feluda. Feluda, by itself, does not collect any data. The data that a model uses depends on the operators applied in a specific application. One can rely on a model like ResNet to cluster similar images. This is a model that captures visual and semantic information about the images. But you could also cluster similar images using a non ML technique like pHash which only captures visual similarity. This is a trade off that you could make to keep your operating cost low or to avoid using a model whose data practices you don't agree with. Feluda frees you up to make those choices and quickly iterate on an approach that gives you desired results while adhering to your constraints. -To understand which operators are being used in an application enabled by Feluda, please check [config-indexer](https://github.com/tattle-made/feluda/blob/master/src/api/config-indexer.yml). You can see the libraries the specific operator relies on, please check the [operator's configuration file](https://github.com/tattle-made/feluda/tree/master/src/api/core/operators). The data collected in the application, and its adherance with various privacy legislation depends on the specific operators enabled in an application. We request you to review the specific operator's data collection practices and compliance with your local laws to see if you should use it in Feluda in your application. +To understand which operators are being used in an application enabled by Feluda, please check [config-indexer](https://github.com/tattle-made/feluda/blob/master/src/config-indexer.yml). You can see the libraries the specific operator relies on, please check the [operator's configuration file](https://github.com/tattle-made/feluda/tree/master/src/core/operators). The data collected in the application, and its adherance with various privacy legislation depends on the specific operators enabled in an application. We request you to review the specific operator's data collection practices and compliance with your local laws to see if you should use it in Feluda in your application. diff --git a/docker-compose-standalone.yml b/docker-compose-standalone.yml deleted file mode 100644 index 2393006a..00000000 --- a/docker-compose-standalone.yml +++ /dev/null @@ -1,37 +0,0 @@ -version: "3.5" - -services: - store: - container_name: es - image: docker.elastic.co/elasticsearch/elasticsearch:7.6.1 - volumes: - - ./.docker/es/data:/usr/share/elasticsearch/data - ports: - - "9300:9300" - - "9200:9200" - environment: - - xpack.security.enabled=false - - discovery.type=single-node - ulimits: - memlock: - soft: -1 - hard: -1 - nofile: - soft: 65536 - hard: 65536 - cap_add: - - IPC_LOCK - - api: - container_name: api - build: - context: ./src - dockerfile: Dockerfile - target: debug - volumes: - - ./src:/app - env_file: ./src/development.env - ports: - - 7000:7000 - - 5678:5678 - command: tail -f /dev/null \ No newline at end of file