Giter Site home page Giter Site logo

writelatex-git-bridge's People

Contributors

alown avatar barrucadu avatar jdleesmiller avatar meis avatar mmazour avatar winstonli avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

writelatex-git-bridge's Issues

automatically generated post back URL may be on a private IP

Currently, the server appears to generate the postback URL automatically, based on an IP address of the machine it's running on. If the machine has multiple IP addresses, it may pick up a private IP address, so the API can't post back to it. It's probably easiest to let the postback root be specified as a config setting.

filemode changes without asking

As I reported in overleaf/overleaf#765, the git bridge Overleaf uses (which I believe to be this one? their fork does not accept issues) changes the filemode from 100755 to 100644 without asking the user. This creates tension between overleaf and non-overleaf users of the same git repository---people add executable permissions intentionally, and the bridge undoes them.

unhelpful error message when trying to clone a protected projects

Since protected projects aren't yet supported, you can't yet clone them. At the moment, we seem to give the generic 'fatal: remote error: Overleaf server not available. Please try again later.' message. It would be better to give a more specific message if possible.

Does this require additional API support?

can we use bare repos to save a bit of disk space?

At the moment, all of the files from the current snap shot are stored in the repo directory. If we can avoid storing them, that will reduce disk usage and give us more options for how we store the repos.

kill the server more gently

Maybe something like this would be safer:

start-stop-daemon --stop --quiet --retry=TERM/60/KILL/5 --pidfile $PIDFILE --name $NAME

the apiKey setting can be removed

We'll just use the basic auth settings to restrict access for now. Better overleaf API support is coming soon, and we can add the appropriate settings then.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.