Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on publishing strategy (NPM/GitHub vs our server) #21

Open
jabooth opened this issue Apr 13, 2017 · 0 comments
Open

Decide on publishing strategy (NPM/GitHub vs our server) #21

jabooth opened this issue Apr 13, 2017 · 0 comments

Comments

@jabooth
Copy link
Contributor

jabooth commented Apr 13, 2017

Option 1 - new builds are pushed to texlive.latexjs.org (with the rest of the texlive mirror).

  • Keeps texlive mirror/releases in lockstep
  • How it's already done
  • Have to serve extra content from our server
  • How to integrate with NPM/GitHub releases

Option 2 - canonical release location is GitHub, with mirror to npm

  • Follows the standards!
  • Fewer things to serve ourselves
  • Have to ensure texlive.latexjs.org and releases are compatible, strong versioning system
  • Isn't implemented

Option 2 has to be the way to go longer term...

@jabooth jabooth changed the title Decide on publishing strategy Decide on publishing strategy (NPM/GitHub vs our server) Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant