3 ms·

Gosh people love complicating things. You don't need docker (a Linux-only piece of tech) to run a java application. Even though I'm on Linux, and docker experi

by koiueo 1y ago

Gosh people love complicating things. You don't need docker (a Linux-only piece of tech) to run a java application. Even though I'm on Linux, and docker experience is waaaaay better here than on any other platform, I wouldn't in my life consider using it to run LanguageTool. java -cp languagetool-server.jar org.languagetool.server.HTTPServer

idoubtit 1y ago
A command without context is not very useful. If anyone wants to run LanguageTool locally, I suggest reading the official documentation page: https://dev.languagetool.org/http-server https://dev.languagetool.org/http-server Their recommended process is : 1. Install fasttext (it's an official Debian package, but you have to compile it on Windows). 2. Download and uncompress the LanguageTool release. 3. Create a config file. 4. Launch the server with the java command (of course, a JRE must be installed). 5. Connect to the API, e.g. with the browser extension. Running a ready-made docker image replaces steps 1-4 and removes the need to install Java globally. Some will prefer it this way.
- deleted 1y ago
  [deleted]
- koiueo 1y ago
  > 2. Download and uncompress the LanguageTool release. > Running a ready-made docker image replaces steps 1-4 We can go pretty low level in the docker option too. 1. Download a Linux installation image 2. Download a hypervisor 3. Install Linux on the virtual machine 4. Install docker in a virtual Linux machine 5. Launch LanguageTool container 6. Configure networking between the host and the container in the guest 7. Connect to the API, e.g. with the browser extension Obviously I initially oversimplified by omitting the configuration step. But adding download step to inflate the complexity is not a fair play ;-) I'd argue that running a platforn-native artifact is both simpler and easier than involving virtualization. Even if steps 1-4 are done by some magical tool like rancher or docker-desktop
itslennysfault 1y ago
Gosh people love complicating things. You don't need to fight with installing (the correct version of) java. I wouldn't in my life consider installing java on my OS directly. For anyone with docker already installed (most people these days)... git clone git@github.com:gardner/LocalLanguageTool.git cd LocalLanguageTool docker compose up

by koiueo 1y ago

idoubtit 1y ago

A command without context is not very useful. If anyone wants to run LanguageTool locally, I suggest reading the official documentation page: https://dev.languagetool.org/http-server https://dev.languagetool.org/http-server Their recommended process is : 1. Install fasttext (it's an official Debian package, but you have to compile it on Windows). 2. Download and uncompress the LanguageTool release. 3. Create a config file. 4. Launch the server with the java command (of course, a JRE must be installed). 5. Connect to the API, e.g. with the browser extension. Running a ready-made docker image replaces steps 1-4 and removes the need to install Java globally. Some will prefer it this way.

deleted 1y ago
[deleted]
koiueo 1y ago
> 2. Download and uncompress the LanguageTool release. > Running a ready-made docker image replaces steps 1-4 We can go pretty low level in the docker option too. 1. Download a Linux installation image 2. Download a hypervisor 3. Install Linux on the virtual machine 4. Install docker in a virtual Linux machine 5. Launch LanguageTool container 6. Configure networking between the host and the container in the guest 7. Connect to the API, e.g. with the browser extension Obviously I initially oversimplified by omitting the configuration step. But adding download step to inflate the complexity is not a fair play ;-) I'd argue that running a platforn-native artifact is both simpler and easier than involving virtualization. Even if steps 1-4 are done by some magical tool like rancher or docker-desktop

itslennysfault 1y ago

Gosh people love complicating things. You don't need to fight with installing (the correct version of) java. I wouldn't in my life consider installing java on my OS directly. For anyone with docker already installed (most people these days)... git clone git@github.com:gardner/LocalLanguageTool.git cd LocalLanguageTool docker compose up