Public Repository

Last pushed: 2 years ago
Short Description
Simple inotify file upload Alfresco connector
Full Description

View project sources.

Workflow

Requirements

Production

  • For production you don't need any special external services, just Docker and Alfresco

Deployment

This application is able to be deployed with the help of docker.
The next sections will help you building a shipable image of the app.

Quick Start

$ docker run -d \ -e 'ALFRESCO_API_URL=http://172.17.42.1:8080/alfresco' \ -e 'ALFRESCO_UPLOAD_DESTINATION=workspace://SpacesStore/6eaff2f4-d419-4e80-bf71-bbcd115715e3' \ -v '/host/path/input:/app/var/input' \ "jack12816/alfresco-connector:0.1.0"

Available Configuration Parameters

  • CONNECTOR_REMOVE_AFTER_UPLOAD: Remove the input file after upload. Defaults to true.
  • ALFRESCO_API_URL: Alfresco application URL. Defaults to http://localhost:8080/alfresco.
  • ALFRESCO_API_USERNAME: Alfresco application username. Defaults to admin.
  • ALFRESCO_API_PASSWORD: Alfresco application password. Defaults to admin.
  • ALFRESCO_UPLOAD_DESTINATION: Alfresco destination folder. Defaults to workspace://SpacesStore/UUID.
  • ALFRESCO_UPLOAD_DESCRIPTION: File description for any upload. Defaults to Uploaded by Alfresco Connector.

Data Volumes

In order to kick off a docker container you need to specify data volumes.
These data volumes should be host bind mounts for this application, but if
you like to store outputs on a docker container volume its fine, too. Anyways
the following examples are host bind mounts.

The watched input path for the daemon inside the container is /app/var/input.
This directory needs to be mounted. See the Quick Start section above.

Docker Pull Command
Owner
jack12816

Comments (0)