@mdwagner I'm really not understanding how this Earthly stuff will work with Windows and the static fixtures. If you happen to find yourself bored sometime, I'd love a second set of eyes on this 😄

Ref: #867 (comment)

I had a thought on this... what if instead of using bash/powershell, it was just a Crystal bootstrap? Would be nice if it could just be Ruby or something to make it a lot faster, but that means a new language requirement. We at least know Crystal will exist when this runs, and things like yarn can just run through Process.

This whole setup script process currently runs several compilations anyway. I think moving to a single Crystal script that just calls the tasks directly would actually make the whole thing faster.

Process.run("shards install")

puts "Installing node dependencies"
Process.run("yarn install --no-progress")

Process.run("yarn dev")

# this replaces lucky db.create, lucky db.verify_connection, and lucky db.migrate
Db::Setup.new.call

Db::Seed::RequiredData.new.call
Db::Seed::SampleData.new.call

I just thought of a downside to this.... One of my favorite features in Lucky is when I go to boot my app on monday morning for work, and it stops to tell me I haven't started all of the necessary services I need to run the app. This is especially great because it takes my app 2 minutes to compile and boot, and waiting that time just to find out redis isn't running would be very annoying....

Now if we move this to Crystal, that means this will take a lot longer to run. On smaller apps it would be negligible, but in larger apps you may be waiting a minute just to find out stuff needs to boot... I guess we just run with this for now and see how it goes.

Edit

Well, this is surprising, and maybe this can't be directly related, but here's a fresh 1.3.0 app running the setup script as it currently stands:

real	1m10.640s
user	1m27.624s
sys	0m38.165s

And here is my take on the Crystal version of this

real	0m43.874s
user	0m41.694s
sys	0m20.983s

One thing I realized is I can't use the Db::.... tasks directly because those require lucky_task which doesn't exist until after you've ran shards install which is ran by this file... a whole catch 22. So I have to just run the lucky db cli tasks through Process.run. Even with that, it seems this is still faster by a little bit. I also noticed that colors weren't showing with the bash version, but they do with the crystal version.

I still think we'll see some issues with lucky dev in larger apps running the system check, but at that point you can come up with your own custom version (i.e. rollback to bash, or handroll some power shell if you want)