Source
jack-novotny•

What is a use case for this? I don’t understand what it’s for.

15
Keith•

To me this looks like yet another "replacement for shell scripts and/or aliases" that often gets posted in r/commandline.

11
StoneColdJane•

noup, its more similar to gulp, or npm scripts.

-2
dev0x0OP•

In short it's like "make" but Ron instead of using one file "makefile", it's split targets to multiple bash files, So you can configure every target with specific env, and you can have binary files for example inside .ron directory, the use cases are endless. I created this tool to help me in a project i'm developing so when I do:

  • "ron start server" it start my dev server
  • "ron start android" it starts android emulator
  • "ron start web" to start web client server
  • "ron start" to start them all
  • "ron build android"
  • "ron build"
  • ... So every one of these targets have a specific configurations and env variables, It will be hard to export and remember all of them.
4
crater2150•

So is there a difference between `ron start server` and simply calling `./.ron/server` except the extra steps? From the sourcecode it doesn't look like your tool handles the env variables, but the executables themselves do.

`make` doesn't just call commands, it manages dependencies between files and commands. For just calling commands, shells can already do that.

5
EverlastingSmokeWorm•

To make it easier to ransomware computers

2†
soullessroentgenium•

I'm with you.

3
jherazob•

General use case Virtualenv, it seems

1
mcandre•

Very cool! What do you think about this one, too?

https://github.com/mcandre/vast

2
dev0x0OP•

Cool this is the first time I see it, I will implement something similar to vast -l that's will be nice to have.

1
mcandre•

Yeah, awesome!

I have some task runners for D and Rust, so you can code task trees directly in those languages!

https://github.com/mcandre/dale

https://github.com/mcandre/tinyrick

1