docker-languagetool VS docker

LanguageTool itself is open source (basic features). I'm running it in a Docker container.

For developers who already have Docker running on their machine. I can strongly recommend running it locally with e.g. Docker Compose.

Safes effort with maintaining an installation and keeping the background process running. Plus, it also works when network connectivity drops.

https://github.com/Erikvl87/docker-languagetool/blob/master/...

Following, you can see my personal docker-compose.yml, which you can use as a reference. For a more detailed description, you can look at the image description erikvl87/languagetool.

I was already used to wiggly lines in my favorite IDE IntelliJ and really missed the spell and grammar check capabilities in other editors especially when writing something in the browser. A colleague told me that IntelliJ is using LanguageTool since I'm pretty satisfied with the analysis inside it. Therefore, I looked around on GitHub for a way of hosting my own LanguageTool server. I came across this repository and decided to give it a go and run it on my Linux server.

It's great, I've been running the self-hosted version for a few months now. I run it using a container[0] on a $10/mo Digital Ocean VPS using Dokku[1]. The main downside is that it's a bit of a memory hog, possible because it's written in Java? Otherwise, I haven't had to mess with it after the initial set up. I like that I'm not sending everything I write to another 3rd party service I don't control.

As for the plugin, it definitely catches more issues than the stock browser spellchecks. The main issue I have with it (maybe someone can point me in the right direction) is that it always tries to autodetect the language. This is fine for longer texts, but often fails on shorter strings like headlines. This leaves my words highlighted red because it thinks I'm writing bad German, or Swedish (which is fair). I haven't been able to figure out how to force it to only use US English.

[0]: https://hub.docker.com/r/erikvl87/languagetool

https://github.com/Erikvl87/docker-languagetool became my daily tool

The entire proof reading engine can be run either through their Java server or in a docker image. Java Docker Another Docker Repo

I have been using this docker version without any issues: https://github.com/Erikvl87/docker-languagetool

Am I better off using this container: https://hub.docker.com/_/nextcloud/

It looks like I'm not the only person who has faced this. apache-based images require buster, for instance, and some docker images that rely on Ruby face issues too (for example, I decided to try setting up Postal but it looks like it's facing the same issues).

If you look at the info on https://hub.docker.com/_/nextcloud, you'll see that you aught to be specifying at least one volume, so that you have the data you want to not disappear on restart, and can access config files.

Yes, and this is what L passed through as the env variables in the docker compose file, as the docs state: https://hub.docker.com/_/nextcloud

You can't map binaries from host to container like this. What you need is a custom Dockerfile that installs ffmpeg. https://github.com/nextcloud/docker/blob/master/.examples/dockerfiles/full/fpm/Dockerfile

A good example to start with is at https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/insecure/postgres/apache

Nextcloud is free and open source. The easiest way to install it is via docker containers. nextcloud docker