Downloadable the: LSR in dismission

Eef Weenink <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.devel
Message-ID <LV3P220MB1224D479CE1ECE1052E5214F86EBA@LV3P220MB1224.NAMP220.PROD.OUTLOOK.COM>
For who has interest.
I prepared a backup-download for the LSR.
You can find all  here:  (it seems to be still online (the last download is from this morning)
https://github.com/eefweenink/LSRDump

Just zip and download.
PS: And hope somebody is able to turn this into a nice new knowledge thing (Maybe using AI to build something).

Regards, Eef

Op 14-10-2025, 21:08 heeft [email protected] <[email protected]> geschreven:

Le lundi 30 juin 2025 à 05:00 +0000, Werner LEMBERG a écrit :
> > the LSR is officially in dismission. I'm moving all my services to
> > some new hardware, and LSR won't be part of the move.  I'll keep
> > around the old hardware for a few months, but then I'll turn it off.
>
> > LSR has been useful, I'm sure, for a lot of people, but by now you
> > can more easily ask to any AI information like that provided by the
> > LSR.  At this point I simply don't have the time to maintain it, and
> > I haven't been using Lilypond in almost 10 years.
>
> > Moving the service is a nightmare because the LSR uses more than a
> > dozen different technologies that must be all configured and
> > synchronized.  Some of those technologies rely on obsolete libraries
> > that have become very difficult to integrate.
>
> > Of course, if someone wants to install and maintain the whole thing
> > elsewhere I can assist.
>
>
> Thanks for the heads-up – and thanks for taking care of the LSR for
> such a long time!
>
> IMHO, the LSR is indispensable for the LilyPond community, and I don't
> think that AI is a viable replacement, especially if you want to
> browse examples or see them rendered.  Alas, I have zero experience
> with writing interactive HTML code that is run on a server...
>
> Anyway, here are some ideas.
>
> * Use 'lsr.lilypond.org' as a new URL.
>
> * Set up the LSR itself as a git repository, mainly to not lose the
>   history of snippets (which seems to be the case right now, AFAIK).
>   From this, a database for searching could be generated on the fly if
>   necessary.
>
> * The code for a new LSR interface should be put into a repository,
>   too.  Given that the LSR is probably not a high-traffic site, I
>   could imagine to use gitlab itself for servicing.  I don't know
>   whether this is possible, though.




Hi folks, revenant here. (I happened to be browsing
the lilypond-devel archives for unrelated reasons.)

I just wanted to mention that there's a lot of wiki
software out there and in particular there is already
a MediaWiki extension (used on Wikipedia) for adding
LilyPond scores.

  https://www.mediawiki.org/wiki/Extension:Score

So that might be an option to get account management,
search, edit history, talk pages, categorization, etc,
without coding all of that yourself. But I have zero
experience as to whether this stuff is easy to install
and maintain.

[Please keep me CCed in replies as I'm not subscribed
to this list anymore.]

Best,
Jean
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.