Private Overleaf and local installation

[chaunguyen2808]

Thanks a lot for this project. I would find it very useful. I have two questions (or requests): (1) Does it work with private overleaf (so the one installed by our university, does that require anything special installation of overleaf: typically, the private overleaf is not that powerful as the one from "real" overleaf.) (2) Can you make it possible to install without administrator requirement?

[aloth]

Hi @chaunguyen2808, thanks for the kind words! Both are covered today:

1. Self-hosted / private Overleaf (incl. ShareLaTeX Community Edition): Yes, olcli supports any self-hosted Overleaf or ShareLaTeX instance via a configurable base URL and session cookie name:

olcli config set-url https://overleaf.your-university.edu
# If your instance uses a different session cookie (default: overleaf_session2).
# Self-hosted Overleaf usually uses overleaf.sid, very old ShareLaTeX instances sharelatex.sid:
olcli config set-cookie-name overleaf.sid

Or per-command with --base-url and --cookie-name, for example olcli --base-url https://overleaf.your-university.edu --cookie-name overleaf.sid list. Your session cookie goes into .olauth or the OVERLEAF_SESSION env var, same as for cloud Overleaf. Endpoints used are the standard ones (/project, /login, zip download, upload, folder, compile), so any reasonably recent Overleaf/ShareLaTeX should work. If you hit a missing endpoint on your university's build, open an issue with the response and I'll look into it.

2. Install without admin/sudo: Use one of these, no admin needed:

• npx (zero install): npx @aloth/olcli list
• Per-user npm prefix:

  mkdir -p ~/.npm-global
  npm config set prefix ~/.npm-global
  export PATH=~/.npm-global/bin:$PATH   # add to ~/.bashrc or ~/.zshrc
  npm install -g @aloth/olcli

• Node version managers like nvm, fnm, or volta. They put Node and global packages in your home directory, so npm install -g never needs sudo.

Hope that helps. Let me know if either path does not work for your setup.

Edit: corrected the first command. It is olcli config set-url; an earlier version of this answer said olcli config base-url, which does not exist.