mirror of
https://github.com/overleaf/overleaf.git
synced 2024-11-21 20:47:08 -05:00
Merge pull request #9139 from overleaf/ae-clsi-readme
Update CLSI README for monorepo GitOrigin-RevId: 9e7fe79cb8de90e72b66532281f71594d8b976ae
This commit is contained in:
parent
805ac00090
commit
d275ee1c68
1 changed files with 33 additions and 21 deletions
|
@ -42,19 +42,26 @@ Installation
|
||||||
|
|
||||||
The CLSI can be installed and set up as part of the entire [Overleaf stack](https://github.com/overleaf/overleaf) (complete with front end editor and document storage), or it can be run as a standalone service. To run is as a standalone service, first checkout this repository:
|
The CLSI can be installed and set up as part of the entire [Overleaf stack](https://github.com/overleaf/overleaf) (complete with front end editor and document storage), or it can be run as a standalone service. To run is as a standalone service, first checkout this repository:
|
||||||
|
|
||||||
$ git clone git@github.com:overleaf/clsi.git
|
```shell
|
||||||
|
git clone git@github.com:overleaf/overleaf.git
|
||||||
|
```
|
||||||
|
|
||||||
Then build the Docker image:
|
Then build the Docker image:
|
||||||
|
|
||||||
$ docker build . -t overleaf/clsi
|
```shell
|
||||||
|
docker build . -t overleaf/clsi -f services/clsi/Dockerfile
|
||||||
|
```
|
||||||
|
|
||||||
Then pull the TeX Live image:
|
Then pull the TeX Live image:
|
||||||
|
|
||||||
$ docker pull texlive/texlive
|
```shell
|
||||||
|
docker pull texlive/texlive
|
||||||
|
```
|
||||||
|
|
||||||
Then start the Docker container:
|
Then start the Docker container:
|
||||||
|
|
||||||
$ docker run --rm \
|
```shell
|
||||||
|
docker run --rm \
|
||||||
-p 127.0.0.1:3013:3013 \
|
-p 127.0.0.1:3013:3013 \
|
||||||
-e LISTEN_ADDRESS=0.0.0.0 \
|
-e LISTEN_ADDRESS=0.0.0.0 \
|
||||||
-e DOCKER_RUNNER=true \
|
-e DOCKER_RUNNER=true \
|
||||||
|
@ -66,6 +73,7 @@ Then start the Docker container:
|
||||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||||
--name clsi \
|
--name clsi \
|
||||||
overleaf/clsi
|
overleaf/clsi
|
||||||
|
```
|
||||||
|
|
||||||
Note: if you're running the CLSI in macOS you may need to use `-v /var/run/docker.sock.raw:/var/run/docker.sock` instead.
|
Note: if you're running the CLSI in macOS you may need to use `-v /var/run/docker.sock.raw:/var/run/docker.sock` instead.
|
||||||
|
|
||||||
|
@ -75,23 +83,27 @@ Important note for Linux users
|
||||||
==============================
|
==============================
|
||||||
|
|
||||||
The Node application runs as user `node` in the CLSI, which has uid `1000`. As a consequence of this, the `compiles` folder gets created on your host with `uid` and `gid` set to `1000`.
|
The Node application runs as user `node` in the CLSI, which has uid `1000`. As a consequence of this, the `compiles` folder gets created on your host with `uid` and `gid` set to `1000`.
|
||||||
```
|
|
||||||
|
```shell
|
||||||
ls -lnd compiles
|
ls -lnd compiles
|
||||||
drwxr-xr-x 2 1000 1000 4096 Mar 19 12:41 compiles
|
|
||||||
```
|
```
|
||||||
|
> `drwxr-xr-x 2 1000 1000 4096 Mar 19 12:41 compiles`
|
||||||
|
|
||||||
If there is a user/group on your host which also happens to have `uid` / `gid` `1000` then that user/group will have ownership of the compiles folder on your host.
|
If there is a user/group on your host which also happens to have `uid` / `gid` `1000` then that user/group will have ownership of the compiles folder on your host.
|
||||||
|
|
||||||
LaTeX runs in the sibling containers as the user specified in the `TEXLIVE_IMAGE_USER` environment variable. In the example above this is set to `root`, which has uid `0`. This creates a problem with the above permissions, as the root user does not have permission to write to subfolders of `compiles`.
|
LaTeX runs in the sibling containers as the user specified in the `TEXLIVE_IMAGE_USER` environment variable. In the example above this is set to `root`, which has uid `0`. This creates a problem with the above permissions, as the root user does not have permission to write to subfolders of `compiles`.
|
||||||
|
|
||||||
A quick fix is to give the `root` group ownership and read write permissions to `compiles`, with `setgid` set so that new subfolders also inherit this ownership:
|
A quick fix is to give the `root` group ownership and read write permissions to `compiles`, with `setgid` set so that new subfolders also inherit this ownership:
|
||||||
```
|
|
||||||
|
```shell
|
||||||
sudo chown -R 1000:root compiles
|
sudo chown -R 1000:root compiles
|
||||||
sudo chmod -R g+w compiles
|
sudo chmod -R g+w compiles
|
||||||
sudo chmod g+s compiles
|
sudo chmod g+s compiles
|
||||||
```
|
```
|
||||||
|
|
||||||
Another solution is to create a `sharelatex` group and add both `root` and the user with `uid` `1000` to it. If the host does not have a user with that `uid`, you will need to create one first.
|
Another solution is to create a `sharelatex` group and add both `root` and the user with `uid` `1000` to it. If the host does not have a user with that `uid`, you will need to create one first.
|
||||||
```
|
|
||||||
|
```shell
|
||||||
sudo useradd --uid 1000 host-node-user # If required
|
sudo useradd --uid 1000 host-node-user # If required
|
||||||
sudo groupadd sharelatex
|
sudo groupadd sharelatex
|
||||||
sudo usermod -a -G sharelatex root
|
sudo usermod -a -G sharelatex root
|
||||||
|
@ -146,7 +158,7 @@ The CLSI is based on a JSON API.
|
||||||
With `curl`, if you place the above JSON in a file called `data.json`, the request would look like this:
|
With `curl`, if you place the above JSON in a file called `data.json`, the request would look like this:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
$ curl -X POST -H 'Content-Type: application/json' -d @data.json http://localhost:3013/project/<id>/compile
|
curl -X POST -H 'Content-Type: application/json' -d @data.json http://localhost:3013/project/<id>/compile
|
||||||
```
|
```
|
||||||
|
|
||||||
You can specify any project-id in the URL, and the files and LaTeX environment will be persisted between requests.
|
You can specify any project-id in the URL, and the files and LaTeX environment will be persisted between requests.
|
||||||
|
|
Loading…
Reference in a new issue