RPE-LibreOffice
Purpose
This software stack provides LibreOffice as a Document Rendering Remote Processing Engine (RPE) through a simple REST API.
Properties
| Stack-Description | LibreOffice Document Rendering Remote Processing Engine (RPE) |
|---|---|
| Stack-Image | docker.msg.team/ps/docker-stack-rpe-libreoffice |
| Stack-Version | 7.1.1 |
| Stack-Release | 20210401 |
| Product-Name | LibreOffice |
| Product-Vendor | The Document Foundation |
| Product-Contact | https://www.libreoffice.org/ |
| Product-Model | Open Source |
| Product-License | MPL |
| Product-Limits | none |
| Implementation Base | C++, Java |
| Execution Base | Operating system - OS, |
| Initial Start Time | 00:01:55 |
| Documentation | https://linux.die.net/man/1/unoconv |
Topology
The stack consists of 1 container:
- rpe-libreoffice: the application is running in this container
Configuration
| Variable Name | Default | Meaning | |
| CFG_LIBREOFFICE_PORT | 3000 | The container is running on Port 3000 |
See also the variables which control integration of the stack into the reverse proxy.
For changes to take effect the stack has to be reinstalled.
First Steps
The rpe-libreoffice Docker Compose stack provides the functionality of UnoConv, a LibreOffice remote conversion API, behind a small REST interface. It allows one to remote convert LibreOffice documents.
$ curl -s --form file=@sample.pptx http://ps4-demo.xt.msg.team/unoconv/pdf >sample.pdf $ curl -s --form file=@sample.pptx http://ps4-demo.xt.msg.team/unoconv/png >sample.png
Administration Commands
REMOVE THIS NOTE
This documents additional commands which are defined in the LABEL section of Dockerfile (docker.stack.exec.XXXXX).
They are executed using docker-stack exec. Only a minority of stacks have such additional commands. Therefore
remove this whole section if it does not apply to the stack you are documenting.
END OF NOTE
Related Documents