Thanks for this Robert. It looks like gogo is indeed the way to go (sounds
good :-)).
What i'm unclear now is wether we should go the route of a provider for
scripting in general, or "just" pipe (which is my direct interest), so
something like a command where first argument specify a context, second is
the actual script
g! sling:script groovy println 'Hello World'
g! sling:script groovy-pipe
p.echo("/content/site").$("sling:resourceType='bar'").mv("/archives")
or direct
g! pipe:run
echo("/content/site").$("sling:resourceType='bar'").mv("/archives")
is there interest from the community for the first case and / or better
ideas for making it less complicated?
2018-05-14 15:49 GMT+02:00 Robert Munteanu <[email protected]>:
> On Mon, 2018-05-14 at 12:05 +0200, Nicolas Peltier wrote:
> > Hey,
> >
> > thought about using terminal rather than felix html page for
> > scripting
> > (when scripting take one line like for pipes, htis might be useful).
>
> The gogo shell can be deployed on Sling and you can make it accessible
> via telnet ( unauthenticated, IIRC ) . I think this can also be doable
> with SSH.
>
> From there you can add new Gogo commands from your bundle or an
> additional Sling Pipes + Gogo shell bundle.
>
> Is that what you're looking for?
>
> Robert
>
