Should we have dedicated installer scripts?

[quintesse]

Right now we tell users to run curl -Ls https://sh.jbang.dev | bash -s - app setup or the extremely ugly iex "& { $(iwr https://ps.jbang.dev) } app setup". Now, it's cool that jbang's own script is completely able to install itself but it makes this first experience with JBang less than ideal.

If we'd have dedicated installer scripts we could simplify to:

curl -Ls https://sh.jbang.dev | sh

and

irm https://ps.jbang.dev -useb | iex

WDYT? Good idea? Bad idea?

[maxandersen]

As in - it would do just bootstrap and then call its own setup?

Makes sense I reckon.

Would we be able to have the old call still work or at least avoid breaking things ? Or we need a new location/dns ?

[quintesse]

Would we be able to have the old call still work or at least avoid breaking things ?

I can imagine that we could create a script that if it has any arguments (other than "app setup") it could automatically start jbang with those arguments after having done it's setup work?

[quintesse]

Well, that would actually be slightly different than what we do now. So perhaps we just skip the setup altogether if any arguments are passed. That way we have two situations:

• without arguments : run jbang app setup
• with arguments : run jbang <arguments>