Using a subdomain as proposed (live.lilypond.org), the whole lilybin stuff could be outsourced to a different server ... finding someone who provides this possibility/server is another story.

But I like the "try it!" approach very much.

Marc

Am 22.02.2017 10:49 vorm. schrieb Phil Holmes <m...@philholmes.net>:

We have a policy of not using server CPU for processing on lilypond.org, because it's donated to us at no cost - so I don't think lilybin could be hosted on the lilypond.org site.

--
Phil Holmes
 
 
----- Original Message -----
From: tisimst
Sent: Tuesday, February 21, 2017 4:55 PM
Subject: Re: LilyBin embedded [WAS: New LilyPond website]



On Mon, Feb 20, 2017 at 9:41 AM, Phil Holmes-2 [via Lilypond] <[hidden email]> wrote:

Lilypond.org gets around 700 sessions per day, according to Google analytics.

--
Phil Holmes
 
 
----- Original Message -----
Sent: Monday, February 20, 2017 3:58 PM
Subject: Re: LilyBin embedded [WAS: New LilyPond website]

I'm primarily responsible for LilyBin. A year or so ago, Timothy Gu (copied) and I got LilyPond running in AWS Lambda, which should be able to handle plenty of traffic. I get 266,667 seconds of free computation time per month from Amazon. We used 38,094 seconds in January for 18,398 requests, meaning we should be able to handle—very roughly estimating—100,000 more requests per month. How many visitors does lilypond.org get?

The LilyBin UI isn't made to be embeddable, but could be made so. I'd probably recommend just wiring up CodeMirror and PDF.js yourself rather than trying to show LilyBin in an iframe.

I'll be happy to work with you if you want a LilyBin-powered demo on the home page!
I love the idea of being able to let visitors try out LP code right there when browsing the home page. I wonder if a dedicated subdomain (e.g., live.lilypond.org) would be more appropriate? 

Here's what I'm thinking. 

Each LP example in the docs has a real source file associated with it, right? So,...

1. Put LilyBin functionality at live.lilypond.org
2. Put all the doc's source files in a directory structure that the new site can access (ideally, through a web-navigate-able directory tree)
3. Place a "Try this live!" link next to each score example in the docs (or the image hyperlink) that points to the specific file in #2 that the visitor can play around with (but can't save over), rather than just linking to a plain text file

This is a wish list, of course, but could be a very cool feature for new/potential users wanting to get their feet wet.

Best,
Abraham


View this message in context: Re: LilyBin embedded [WAS: New LilyPond website]
Sent from the User mailing list archive at Nabble.com.


_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to