this post was submitted on 16 Dec 2023
34 points (92.5% liked)

Selfhosted

40313 readers
185 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Do any of you self-host Overleaf? I know there is a Docker project, but from what I've heard it's not easy to install. The Yunohost version used to work but didn't support file upload, so that makes it bad too.

Have any of you successfully installed Overleaf with e.g. Docker and it works just fine? If so, could any of you share e.g. the Docker Compose file?

you are viewing a single comment's thread
view the rest of the comments
[–] november@iusearchlinux.fyi 8 points 11 months ago* (last edited 11 months ago) (2 children)

There's some tinkering with their docker-compose.yml to make it work. Here's mine you can copy if you want to get it up and running. I don't use nginx or any reverse-proxy btw. All data is saved in their own individual volumes which you can back up:

services:
    sharelatex:
        restart: always
        image: sharelatex/sharelatex
        depends_on:
            mongo:
                condition: service_healthy
            redis:
                condition: service_started
        ports:
            - *DESIRED_PORT*:80
        links:
            - mongo
            - redis
        stop_grace_period: 60s
        volumes:
            - data:/var/lib/sharelatex
            - texlive:/usr/local/texlive

        environment:
            SHARELATEX_APP_NAME: Overleaf Community Edition
            SHARELATEX_MONGO_URL: mongodb://mongo/sharelatex
            SHARELATEX_REDIS_HOST: redis
            REDIS_HOST: redis
            ENABLED_LINKED_FILE_TYPES: 'project_file,project_output_file'
            ENABLE_CONVERSIONS: 'true'
            EMAIL_CONFIRMATION_DISABLED: 'true'

    mongo:
        command: "--replSet overleaf"
        restart: always
        image: mongo:4.4
        expose:
            - 27017
        volumes:
            - mongo_data:/data/db
        healthcheck:
            test: echo 'db.stats().ok' | mongo localhost:27017/test --quiet
            interval: 10s
            timeout: 10s
            retries: 5

    redis:
        restart: always
        image: redis:6.2
        expose:
            - 6379
        volumes:
            - redis_data:/data

volumes:
  data:
  mongo_data:
  redis_data:
  texlive:

Some of my documents rely on certain packages which didn't come with the Docker image. You will need to run
docker exec sharelatex-sharelatex-1 tlmgr update --self;docker exec sharelatex-sharelatex-1 tlmgr install scheme-full
so that you can render your documents properly if they utilize certain packages.

Optionally—since the full scheme takes about 8 GB and you may not need everything—you can replace scheme-full with a different scheme you can find by running
docker exec sharelatex-sharelatex-1 tlmgr info schemes
The i before any scheme name means that it is already installed.

Update:
Included a texlive volume to save any packages that were installed, so when recreating the containers, they will persist.

[–] Keelhaul@sh.itjust.works 1 points 11 months ago (1 children)

Are the packages installed to a persistent volume? Or do they need to be reinstalled after recreating the container?

[–] november@iusearchlinux.fyi 2 points 11 months ago* (last edited 11 months ago)

I checked the volumes that I included in the compose file, and looked for either a texlive, tlmgr or a package folder and didn't find anything. I think it's safe to assume that you would need to reinstall the packages if you recreated the containers.

~~This is a problem that I didn't consider. I will try to make an update to my compose file that will keep the packages persistent.~~

Check above for the update!