[GH-ISSUE #9679] LanguageTool #2123

New issue

Closed

opened 2026-02-26 12:51:23 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:51:23 +03:00

Owner

Originally created by @evanre on GitHub (Dec 5, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9679

🌟 Briefly describe the feature

Add script for LanguageTool

📝 Detailed description

LanguageTool is an open-source proofreading tool for English, French, German, Polish, Russian, and more than 20 other languages. It can detect many grammar and style issues that a simple spell checker will miss.

Recently the LanguageTool team has started limiting / deprecating free usage for the official browser extension and cloud service. However, because the core project is open source, it is still possible to self-host LanguageTool and point the browser extension (or other clients) to a custom server instead of their cloud.

There are already community Docker images (for example erikvl87/languagetool) and various guides on how to run LanguageTool in a container, but setting this up manually still requires some effort:

provisioning a container or VM,
installing Java / pulling the image,
setting sane memory limits (LanguageTool can be quite RAM-hungry),
exposing the API on a local URL/port,
optionally putting it behind a reverse proxy with TLS.

I’d like to request a community script for Proxmox VE that automates deployment of a self-hosted LanguageTool instance. For example, a script that:

creates an LXC container (or VM) with recommended resources (e.g. 1–2 vCPU, 2–4 GB RAM),
installs and configures LanguageTool, either:
- via a Docker image, or
- directly via the official JAR,
configures reasonable Java heap limits and basic logging,
exposes the HTTP API on a configurable port (e.g. http://pve-lt.local:8010),
optionally sets up a simple reverse proxy with TLS (nginx/Traefik/Caddy), so the browser extension can connect over HTTPS.

A minimal version (no reverse proxy, just an HTTP API inside the LAN) would already be very helpful. Advanced options (TLS, n-gram data, custom memory limits) could be exposed as script parameters.

💡 Why is this useful?

Privacy & control: All text stays on the user’s own infrastructure instead of being sent to a third-party cloud service. This is important for anyone handling internal documentation, customer data, or other sensitive content.
Future-proofing: If the free plans or terms for the official LanguageTool cloud continue to change, self-hosting ensures users can keep using the same functionality without relying on pricing or policy decisions of a commercial service.
Multi-language proofreading for homelabs: LanguageTool supports many languages out of the box (including English, Polish, German, etc.), making it a great addition to a Proxmox-based homelab where people already host services like Wikis, documentation portals, or note-taking apps.
Lower barrier for self-hosting: While it is possible to deploy LanguageTool manually, a ready-to-use Proxmox VE community script would make it much easier and more consistent — especially for users who are comfortable with Proxmox but don’t want to spend time on Java/Docker tuning, reverse proxies, and memory parameters.
Nice fit for existing Proxmox setups: Many Proxmox users already run containers for things like Git, documentation, and collaboration tools. A “one-command” script to add a LanguageTool container would integrate naturally into this ecosystem and encourage more people to self-host their proofreading instead of relying on external SaaS.

In short, a LanguageTool script would add a privacy-friendly, multi-language grammar checker to the catalog of community scripts and help more Proxmox VE users get a robust, self-hosted alternative to the official LanguageTool cloud.

Originally created by @evanre on GitHub (Dec 5, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9679 ### 🌟 Briefly describe the feature Add script for LanguageTool ### 📝 Detailed description [LanguageTool](https://www.languagetool.org/) is an open-source proofreading tool for English, French, German, Polish, Russian, and [more than 20 other languages](https://languagetool.org/languages/). It can detect many grammar and style issues that a simple spell checker will miss. Recently the LanguageTool team has started limiting / deprecating free usage for the official browser extension and cloud service. However, because the core project is open source, it is still possible to self-host LanguageTool and point the browser extension (or other clients) to a custom server instead of their cloud. There are already community Docker images (for example `erikvl87/languagetool`) and various guides on how to run LanguageTool in a container, but setting this up manually still requires some effort: - provisioning a container or VM, - installing Java / pulling the image, - setting sane memory limits (LanguageTool can be quite RAM-hungry), - exposing the API on a local URL/port, - optionally putting it behind a reverse proxy with TLS. I’d like to request a **community script for Proxmox VE** that automates deployment of a self-hosted LanguageTool instance. For example, a script that: - creates an LXC container (or VM) with recommended resources (e.g. 1–2 vCPU, 2–4 GB RAM), - installs and configures LanguageTool, either: - via a Docker image, or - directly via the official JAR, - configures reasonable Java heap limits and basic logging, - exposes the HTTP API on a configurable port (e.g. `http://pve-lt.local:8010`), - optionally sets up a simple reverse proxy with TLS (nginx/Traefik/Caddy), so the browser extension can connect over HTTPS. A minimal version (no reverse proxy, just an HTTP API inside the LAN) would already be very helpful. Advanced options (TLS, n-gram data, custom memory limits) could be exposed as script parameters. ### 💡 Why is this useful? - **Privacy & control**: All text stays on the user’s own infrastructure instead of being sent to a third-party cloud service. This is important for anyone handling internal documentation, customer data, or other sensitive content. - **Future-proofing**: If the free plans or terms for the official LanguageTool cloud continue to change, self-hosting ensures users can keep using the same functionality without relying on pricing or policy decisions of a commercial service. - **Multi-language proofreading for homelabs**: LanguageTool supports many languages out of the box (including English, Polish, German, etc.), making it a great addition to a Proxmox-based homelab where people already host services like Wikis, documentation portals, or note-taking apps. - **Lower barrier for self-hosting**: While it is possible to deploy LanguageTool manually, a ready-to-use Proxmox VE community script would make it much easier and more consistent — especially for users who are comfortable with Proxmox but don’t want to spend time on Java/Docker tuning, reverse proxies, and memory parameters. - **Nice fit for existing Proxmox setups**: Many Proxmox users already run containers for things like Git, documentation, and collaboration tools. A “one-command” script to add a LanguageTool container would integrate naturally into this ecosystem and encourage more people to self-host their proofreading instead of relying on external SaaS. In short, a LanguageTool script would add a privacy-friendly, multi-language grammar checker to the catalog of community scripts and help more Proxmox VE users get a robust, self-hosted alternative to the official LanguageTool cloud.

kerem

2026-02-26 12:51:23 +03:00

closed this issue
added the
enhancement
label

kerem referenced this issue

2026-02-26 13:33:53 +03:00

[PR #2123] [MERGED] New Script: SearXNG #3553

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2123

No description provided.

Rows
Columns