Ticker
Ticker is a self-hosted live-message ticker that displays a single scrolling strip of text on a public web page.
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.
66/100 Good
- Maintained
- 100last commit 19 days ago
- Popular
- 2313 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 602 GB minimum RAM, runs on ARM
- Security check
- 100no serious findings, CI, tests
- GitHub stars
- 13
- Open issues
- 6
- Last commit
- 2026-11-01
- Latest release
- 4.1.3
- License
- GPL-3.0
- Activity
- steady
Checked 4 days ago - source: GitHub (systemli/ticker-frontend)
Resources & Compatibility
Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Replace the placeholder credentials first Before the service starts, replace the API key, API secret, callback URL, and node name in the Node.js setup. These settings identify your app and tell TickerQ where to send job results, so missing or wrong values will prevent scheduled tasks from working. source
- Keep port 3000 open The example runs the Node.js service on port 3000, which is the number computers use to reach it. If the port is blocked or already used, TickerQ cannot send job requests to your app, so keep it open or change the setting. source
- Choose immediate or manual startup You can make TickerQ start right away, which is the default, or start it later in code. Starting manually is useful when other parts of your app are not ready yet, because it prevents jobs from running too early. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does the ticker frontend store my portfolio data itself?
No, the ticker frontend is a static single-page application and holds no data of its own. All data lives in the ticker API.
Why does the frontend show that the ticker is inactive?
The ticker API selects the ticker from the request Origin header. That address must be registered under the ticker's websites in the admin interface.
Which port does the frontend dev server use and how does it reach the API?
The dev server uses port 4000. It proxies API requests to the ticker API on port 8080.
Does PWA install behaviour work during local development?
No, the service worker is only registered in production builds. PWA behaviour does not appear when using the dev server.
Is the frontend published as a Docker image?
Yes, the published Docker image is systemli/ticker-frontend. The project documentation also covers running the full stack with Docker.
Answers sourced from github.com
Community
Collected 48 days ago - public community threads