Re: LSR in dismission

Luca Fascione <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.devel
Message-ID <CAN3Q5NgvLEtaafHizOxDVHBOzhaCyJ_rgcV5akR69bvqntaT=A@mail.gmail.com>
On Mon, Jun 30, 2025 at 7:12 PM Sebastiano Vigna <[email protected]>
wrote:

> > On 30 Jun 2025, at 17:36, Luca Fascione <[email protected]> wrote:
> > What kind of hardware do we need to run this? How much traffic does the
> server see?
>
> In a week I see 2500 non-bot IPs.

 < ... >


> Everything is very small. I mean, the DB is 10MB.
>

I think I own suitable hardware to run this on actually...
What I'm less sure about is what kind of access does my ISP allow "going
in".


> > Werner:
> >  - if we have the snippets in a "one snippet per file" setup in gitlab
> (or something of that general flavour), what purpose does MySQL serve?
> >  - it seems to me in this scenario the backend of LSR would simply be a
> "cron job" that runs "git pull" once at midnight and then regenerates all
> the images missing from new snippets (if any)? What am I missing here?
> >  - I guess in this scenario the "contribution interface" is simply
> someone that approves a "pull request" on the gitlab repo...
>
> Yes, that might work.


Nice.


> If you want to sandbox lilypond when you execute the snippets you have to
> cage it (I wrote the Lilypond code that make caging possible).
>

What's the purpose of this "caging"? Is it security against malicious code,
or more protection from non-malicious run-away processes? What's the
thinking?
Also what does your cage do? What is it robust to?

L


-- 
Luca Fascione
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.