Skip to main content

Overleaf Two-Way Sync Tool

Project description

Overleaf community edition sync

A working fork of overleaf-sync by moritzgloeckl, who has not been active for over 2 years. Btw the code is weirdly architected. I gathered 2 pull requests from ashmat98 (fix the upload) and mone27 (add Community Edition support), so thanks to them for their work.

Easy Overleaf Two-Way Synchronization

This tool provides an easy way to synchronize Overleaf projects from and to your local computer. No paid account necessary.


Features

  • Sync your locally modified .tex (and other) files to your Overleaf projects
  • Sync your remotely modified .tex (and other) files to computer
  • Works with free Overleaf account
  • No Git or Dropbox required
  • Does not steal or store your login credentials (works with a persisted cookie, logging in is done on the original Overleaf website)

How To Use

Install

The package is available via PyPI. Just run:

moritz@github:~/test$ pip3 install overleaf-sync

That's it! Depending on your local Python installation, you might need to use pip instead of pip3.

Prerequisites

  • Create your project on Overleaf, for example a project named test. Overleaf-sync is not able to create projects (yet).
  • Create a folder, preferably with the same name as the project (test) on your computer.
  • Execute the script from that folder (test).
  • If you do not specify the project name, overleaf-sync uses the current folder's name as the project name.

Usage

Login

moritz@github:~/test$ ols login [--path]
Login successful. Cookie persisted as `.olauth`. You may now sync your project.

Logging in will be handled by a mini web browser opening on your device (using Qt5). You can then enter your username and password securely on the official Overleaf website. You might get asked to solve a CAPTCHA in the process. Your credentials are sent to Overleaf over HTTPS.

It then stores your cookie (not your login credentials) in a hidden file called .olauth in the same folder you run the command from. It is possible to store the cookie elsewhere using the --path option. The cookie file will not be synced to or from Overleaf.

Keep the .olauth file save, as it can be used to log in into your account.

Listing all projects

moritz@github:~/test$ ols list [--store-path -v/--verbose]
10/31/2021, 01:23:45 - Project A
09/21/2020, 01:23:45 - Project B
08/11/2019, 01:23:45 - Project C
07/01/2018, 01:23:45 - Project D

Use ols list to conveniently list all projects in your account available for syncing.

Downloading project's PDF

moritz@github:~/test$ ols download [--name --download-path --store-path -v/--verbose]

Use ols download to compile and download your project's PDF. Specify a download path if you do not want to store the PDF file in the current folder. Currently only downloads the first PDF file it finds.

Syncing

moritz@github:~/test$ ols [-l/--local-only -r/--remote-only --store-path -p/--path -i/--olignore]

Just calling ols will two-way sync your project. When there are changes both locally, and remotely you will be asked which file to keep. Using the -l or -r option you can specify to either sync local project files to Overleaf only or Overleaf files to local ones only respectively. When using these options you can also sync deleted files. If a file has been deleted it can either be deleted on the target (remote when -l, local when -r) as well, restored on the source (local when -l, remote when -r) or ignored.

The option --store-path specifies the path of the cookie file created by the login command. If you did not change its path, you do not need to specify this argument. The -p/--path option allows you to specify a different sync folder than the one you're calling ols from. The -i/--olignore option allows you to specify the path of an .olignore file. It uses fnmatch internally, so it may have some similarity to .gitignore but doesn't work exactly the same. For example, if you wish to exclude a specific folder named out, you need to specify it as out/*. See here for more information.

Sample Output:

Project queried successfully.
✅  Querying project
Project downloaded successfully.
✅  Downloading project

Syncing files from remote to local
====================

[SYNCING] report.tex
report.tex does not exist on local. Creating file.

[SYNCING] other-report.tex
other-report.tex does not exist on local. Creating file.


✅  Syncing files from remote to local

Known Bugs

  • When modifying a file on Overleaf and immediately syncing afterwards, the tool might not detect the changes. Please allow 1-2 minutes after modifying a file on Overleaf before syncing it to your local computer.

Contributing

All pull requests and change/feature requests are welcome.

Disclaimer

THE AUTHOR OF THIS SOFTWARE AND THIS SOFTWARE IS NOT ENDORSED BY, DIRECTLY AFFILIATED WITH, MAINTAINED, AUTHORIZED, OR SPONSORED BY OVERLEAF OR WRITELATEX LIMITED. ALL PRODUCT AND COMPANY NAMES ARE THE REGISTERED TRADEMARKS OF THEIR ORIGINAL OWNERS. THE USE OF ANY TRADE NAME OR TRADEMARK IS FOR IDENTIFICATION AND REFERENCE PURPOSES ONLY AND DOES NOT IMPLY ANY ASSOCIATION WITH THE TRADEMARK HOLDER OF THEIR PRODUCT BRAND.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THIS SOFTWARE WAS DESIGNED TO BE USED ONLY FOR RESEARCH PURPOSES. THIS SOFTWARE COMES WITH NO WARRANTIES OF ANY KIND WHATSOEVER. USE IT AT YOUR OWN RISK! IF THESE TERMS ARE NOT ACCEPTABLE, YOU AREN'T ALLOWED TO USE THE CODE.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

overleaf_sync_ce-2.0.0.tar.gz (14.8 kB view details)

Uploaded Source

Built Distribution

overleaf_sync_ce-2.0.0-py3-none-any.whl (13.7 kB view details)

Uploaded Python 3

File details

Details for the file overleaf_sync_ce-2.0.0.tar.gz.

File metadata

  • Download URL: overleaf_sync_ce-2.0.0.tar.gz
  • Upload date:
  • Size: 14.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.0.0 CPython/3.11.7

File hashes

Hashes for overleaf_sync_ce-2.0.0.tar.gz
Algorithm Hash digest
SHA256 70c2bffde45e17a5abd5bd8c3175701a2cbc92754e2d265074f3f026a7de2b8a
MD5 cd555a8329c5446f4d150108f81efb3c
BLAKE2b-256 cab8794a806c2c54a93cea089507a8a9c3304814402e4fc674d62b19266ff063

See more details on using hashes here.

File details

Details for the file overleaf_sync_ce-2.0.0-py3-none-any.whl.

File metadata

File hashes

Hashes for overleaf_sync_ce-2.0.0-py3-none-any.whl
Algorithm Hash digest
SHA256 425dbd70d9993b8374c474fb7d65a75516efd35c502d2182cd7d09dec1f77e36
MD5 ff0c07c1a8722efc24abc7f7643ba54f
BLAKE2b-256 3aefee6f02bdcd7ab71f6eed9626e0035b87608b002d117fad8ed0339d6dfdc4

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page