Blurit On-Premise Documentation
2.0.7
2.0.7
  • Blurit On-Premise
    • 🚀Getting started
    • 💻Requirements
    • 🖊️Installation
      • Linux dependencies
      • Windows dependencies (WSL)
      • Configuration
      • Run BlurIt OP
      • Multi-servers installation
      • Post installation verifications
    • 🎇Usage
      • Manager Webapp
      • API
        • License
        • Tasks
          • Process a directory
          • Process a file
          • Get the status of a task
      • Command line interface
      • Monitoring With Flower
    • Release notes
  • CLOUD IMAGES
    • Introduction
    • AWS
Powered by GitBook
On this page
  1. Blurit On-Premise

Usage

PreviousPost installation verificationsNextManager Webapp

Last updated 2 months ago

As said in the section, BlurIt OP Web Manager or API works within the paths set in LOCAL_STORAGE_INPUT_PATH and LOCAL_STORAGE_OUTPUT_PATH. Every processed media will be stored in LOCAL_STORAGE_OUTPUT_PATH, while the original media will be processed from LOCAL_STORAGE_INPUT_PATH.

There are two ways to process files with BlurIt OP:

  1. Manager Webapp: The web app manager provides a Graphical User Interface (GUI) accessible at http://<host> or https://<host>, where "host" refers to the IP address of the machine where BlurIt OP is deployed or the dns url configured. This interface allows non-developers to process files easily.

  2. API: The API is accessible at http://<host>/api or https://<host>/api. It allows developers to integrate BlurIt OP file processing capabilities into their own applications or workflows programmatically. This allows for greater flexibility and automation.

🎇
Configuration