jack dempsey
jack dempsey
Any status on this? Started to work on heroku today and just saw this. My own $.02 regarding configuration, etc: it should do the simplest thing that could work for...
Cedar's definitely the way to go (IMHO). Push for latest version of ruby, rails, and support for other things like node, etc.
Any updates on this? Would like to help get the heroku scroll to a place where it's usable, even if not hugely fully featured.
Cool! Feel free to shout if any little assistance is desired.
hey @hone still interested in this? I'm tired of forgetting about setting config.assets.initialize_on_precompile = false every damn time + other things...Can I help?
Seems like a ~/.scrolls dir might be desired from other pull requests? Maybe makes sense to standardize that, and then the file that stores this data can go in there?
Yep, definitely like that style of use. You could even publish scrolls that represent common configs, etc. So, how do we build this? It would seem that if scrolls had...
Ahh, just found the require option after looking through source. Seems this would do it. I'm going to give this idea a go and see how it turns out.
Ok, code is ugly (partial copy/paste from rake task), but is proof-of-concept ready. I like this strategy. Would probably want to combine with other efforts to write out scroll file...
Ok so it automatically writes a history file that you then select from? I can see that working nicely. 1. Every time you run scrolls we add to a history...