3 ms·
The simplest one that I also use the most is start.sh: https://github.com/JangoSteve/start https://github.com/JangoSteve/start I've been using it for 3 years n
by JangoSteve 10y ago
The simplest one that I also use the most is start.sh: https://github.com/JangoSteve/start https://github.com/JangoSteve/start
I've been using it for 3 years now, but keep forgetting to tell anyone about it. It's a simple bash script that detects what kind of project your current directory is and runs the appropriate command to start the development server.
I created it, because I found myself constantly switching between projects of different types, and it always took me a few moments to remember if the current project was Rails 2 or Rails 3/4, Node, Jekyll, Rack app, etc. and starting the development server on port 3000 was starting to take 2 or 3 tries before getting it right.
Now, I just cd into any project and run `start`. It currently detects Foreman projects, Rails (old and new), Jekyll (old and new), Gollum, plain Rack apps, and Node; and it's easy to add new things as well.
- vram22 10y agoInnovative idea ...
- JangoSteve 10y agoThanks!
- loopbit 10y agoThanks for sharing, will definitely use it! As a somewhat related tool, I started using autoenv (https://github.com/kennethreitz/autoenv https://github.com/kennethreitz/autoenv) a while ago (automatically sources a .env file when you cd into the directory). I use it to set environment variables, start docker images...
- lucb1e 10y agoThis sounds like one of those things that might, with some luck and maintenance, become a universal thing. My first reaction was "why would I need this, surely I can type the appropriate build/run command for the environment I'm developing in?" but I might just end up going "okay this is extremely practical", especially after running some open source projects from a git clone.