LinTO Platform Business Logic Server
LinTO Platform Business Logic Server is the workflow engine of the LinTO voice assistant platform, executing the tasks and skills you configure your assistant…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
6/100 Low
- Maintained
- 0last commit 2725 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2019-06-06
- Activity
- stale
Checked yesterday - source: GitHub (aesmin/linto-platform-stack)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Part of the LinTO platform stack BLS is a mandatory component of a complete LinTO platform stack and the main process that executes workflows defined as collections of LinTO skills; deploy it together with the rest of the stack. source
Fetched 48 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I have to run the Business Logic Server by itself?
No. BLS is a mandatory component of a complete LinTO platform stack and should be deployed together with the rest of the stack.
How do the LinTO services communicate when deployed with Docker?
Create an attachable Docker network, such as linto_net, before starting the stack. The compose files use that network for inter-service communication.
Where should I look for environment configuration?
The stack README marks ENV as work in progress and says configuration data can be found in each GitHub repository.
Which compose files are included in the full-stack example?
The example runs nginx-ingress, Tock, admin, business-logic-server, mqtt-broker, overwatch, STT, and haproxy together with docker-compose. Each service has its own compose file in its folder.
Are prebuilt images available for deployment?
Yes. The stack page says LinTO Platform pre-compiled Docker images for Linux docker orchestrated infrastructures are available in the Docker Hub registry.
Answers sourced from github.com, github.com, hub.docker.com
Community
Collected 48 days ago - public community threads