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

LAAS - lilypond as a service #59

Open
noteflakes opened this issue Feb 5, 2018 · 0 comments
Open

LAAS - lilypond as a service #59

noteflakes opened this issue Feb 5, 2018 · 0 comments

Comments

@noteflakes
Copy link
Collaborator

noteflakes commented Feb 5, 2018

Features:

  • A server offering a lilypond compilation service - user uploads a snippet or a complete file or a complete file archive including all dependencies, the server generates the target file.
  • Support for all applicable command line switches (i.e. relating to output).
  • Support for different version of lilypond.
  • Support for lyp packages (as long as they can be found - those on the lyp package index, or those with a URL).
  • Should be fast (as possible).
  • Should cache output files on disk (in /tmp perhaps?).

Additional tooling:

  • Linux/MacOS - bash script for compiling from shell.
  • Windows - batch file for compiling from shell.

What needs to be added to lyp?

  • HTTP server (on arbitrary port) and accept HTTP requests for compiling files, along with command line arguments.
  • Cache output file (hash input files and command line arguments) in /tmp.
  • Automatic installation of requested lilypond version, if not already installed.
  • Process separation to limit security exposure (use lys?)

Another possibility is to create an external tool that will use lyp as a ruby dependency (actually an interesting use case).

@noteflakes noteflakes changed the title LAAP - lilypond as a service LAAS - lilypond as a service Feb 6, 2018
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