News for hackers. Stuff that matters.
Re:Fast Rails updates through minimal dependencies by radimm on Friday January 11, 2013 @09:14AM (#5042713)
It's always good to use Vagrant (or any other method to be quickly able to refresh the dev environment) and routinely do destroy/up. This is for me so far the best precaution to keep the application light on dependencies.
Re:Fast Rails updates through minimal dependencies by Manfred on Friday January 11, 2013 @09:23AM (#5042755)
I wholeheartedly agree, it's actually something I wanted to write about. A maintainable application should be up and running with a seeded database in a few commands; i.e.: gem install bundler && ./script/install.
Re:Fast Rails updates through minimal dependencies by Volpe on Friday January 11, 2013 @10:13AM (#5042966)
That's fine if it's a ToDo list app. But if your app integrates with other services applications... it needs those running as well.

The more services/external dependencies you cram into single commands... the more maintenance (of that cramming) is required.

Re:Fast Rails updates through minimal dependencies by Manfred on Friday January 11, 2013 @10:58AM (#5043186)
That just means you have to try a bit harder (;

I agree that it's not always possible to set up everything automatically but with a shared encrypted filesystem, good instructions, and tools like Foreman you can go a long way.

In case something can't be set up automatically we usually have a clear README and the initializer prints a note about where to find instructions about getting it running.

Maintaining the install script isn't much more painful then setting up it by hand, especially if you make sure the script is ‘reentrant’.