40
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Apr 2024
40 points (95.5% liked)
Open Source
31358 readers
195 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
This is probably not the solution for most, but if you care, overleaf can be selfhosted.
More info here: https://github.com/overleaf/overleaf
Edit: note->not
Just FYI, I've done this, and if you're not super familiar with Docker network permissions it can be more than a bit funky, especially if you're on Windows. I'm sure it's trivial for folks who're used to docker, but getting the right ports configured is a bit of a pain.
Idk when you did it, but with the overleaf toolkit, at least the docker networking seems to be no problem. I had quite some problems with updating though. I run an outdated version at the moment because texlive gets updated faster than overleaf, which produces errors when installing the texlive full package. Overall, also can’t recommend.
Oh I got it running eventually. If you were on Linux, it'd be fine, but since on Windows the docker engine runs inside WSL, the ports exposed to a browser in Windows are not the same as what Overleaf is trying to expose in WSL.
I see, you probably had to change the overleaf config file? I feel it’s too much work to keep it updated and running, on my Linux server. But the official overleaf is just too slow. It struggles to compile 30 page documents, and i have several that are longer. How does it run for you on your windows computer, with the local installation? What are the specs of your machine?
LaTeX is just fundamentally not that fast, especially when pulling in lots of packages. I'm running it on a server with a i7-12700K and 64 GB of RAM, but I didn't really notice a slowdown when running it on an old laptop, they're both about the same speed as the official overleaf. With longer or more complex documents, I usually split it into multiple files and edit them on their own, then use
\include{}to being them into the final file with proper formatting and the right preamble. Of course, thats using a local MikTeX install, so YMMV.To be honest, I've always wondered why you can't like "pre-compile" a bunch of packages into a binary and
includethat to speed things up. I'm sure there are good reasons, I just don't know them.You are correct, LaTeX isn’t very fast in general, but my 8 core ryzen server with 8GB of ram assigned to the vm running overleaf is usually twice as fast as the official overleaf unpaid tier. The specs you listed should produce much better results than the official overleaf. This seems weird to me.
As an example, I just compiled my thesis, which is about 60 pages, lots of references, pictures, and generally a heavy document. On my server it takes about 35 seconds, the official overleaf just times out (pay or we won’t compile your document).
Hmmm I guess I haven't really compared them on documents over about 20 pages, and even then it was just a qualitative judgment.
I've tried, but it was not easy at all and I sadly finally gave up because it uses Redis and that Redis needs some specific instructions that are not available for old/low end CPUs like the one I have in my homelab. The best self-hosted alternative I found at the time was FidusWriter. Probably not the best solution for OP, but still an OK self-hosted alternative to Overleaf.