There are other methods, e.g. it’s probably available in all major distros’ package managers right now, as well as in Homebrew on macOS and Choco on Windows.
And curl|bash alone is probably okay-ish? You’re still running the code ultimately, so you either trust it or not. It’s what I use for my own project (with a twist: you get the chance to read the script before you run it): https://lunni.dev/docs/install/
But combined with the “ai_personal_chef” it really tripped me off. What the hell is that even supposed to mean? Do I pipe a code written by LLM directly into my shell? (Probably not, it would be pretty expensive for them to run that.)
Ahhhh, okay! Looks like I’ve got a bad roll of a dice then. (The `uber_for` is actually hilarious :-)
Maybe move the script to something like ash-hq.org/new?project_name={generated}, so that it’s easier to guess what’s going on? Or break it up into steps, like:
# Install prerequisites (Elixir and `igniter_new`):
curl -fsSo 'https://ash-hq.org/install?with=phoenix' | sh
# Create a new app:
mix igniter.new {{ generated }} --yes-to-deps --yes --install ""
cd {{ generated }}
# Install Ash:
mix igniter.install ...
(This could also let you eliminate that “Already have an app?” button-link – the users can just skip the steps they’ve already done.)
And curl|bash alone is probably okay-ish? You’re still running the code ultimately, so you either trust it or not. It’s what I use for my own project (with a twist: you get the chance to read the script before you run it): https://lunni.dev/docs/install/
But combined with the “ai_personal_chef” it really tripped me off. What the hell is that even supposed to mean? Do I pipe a code written by LLM directly into my shell? (Probably not, it would be pretty expensive for them to run that.)