HN user

twe4ked

25 karma

[ my public key: https://keybase.io/odin; my proof: https://keybase.io/odin/sigs/8r421QEKM378bhxKXl5WvZeZuq0qY2je-5dv3-tk2yw ]

Posts1
Comments17
View on HN

> Some of us spend more time doing productive work than pissing around making our editors and shells and whatnot all pretty.

Some of us enjoy this and therefore tools that make it easier, better or more fun are always welcome.

People are finding ways to solve problems that have existed for decades. I don't see how this is something coming from _hipster web devs_.

> Come on guys.

Stop solving your problems? If you don't see any value in it move on.

The idea with modularizing things is it makes it easy to share the parts that people do want the same. Where I work we have slowly but surely come to an agreement on most of our git aliases. That's why we built [fresh] a similar tool to allow us to share the parts we want to. [fresh] allows us to easily override anything we don't like and keep the parts we do like up to date. My [freshrc] file is an example of mixing other peoples aliases and bin files with a collection of my own config.

[fresh]: https://github.com/freshshell/fresh

[freshrc]: https://github.com/twe4ked/dotfiles/blob/master/freshrc

Here's the install script (https://raw.github.com/freshshell/fresh/master/install.sh). You can have a read though if you like. I don't know any safer ways to install applications. SSL is a good idea though.

We will add some more info to the home page but we were trying to keep most of the info in the README.

> The GitHub README doesn't really have any information about what it is either.

What else would you like to know?

The batch mode is a good idea, however the way we're doing it is a tried and true method used by many dev tools Bundler, Vundle, etc.

At the moment Koi Deploy allows you to add GitHub repositories as 'Projects' and set up multiple Heroku instances for that project. You can then schedule or instantly deploy your application from any branch/git ref with the click of a button.

The deploy process:

* Turns on maintenance mode

* Does a backup of your database using pgbackups (support for others later)

* Pushes your code to Heroku

* Runs migrations

* Turns off maintenance mode

* Sends you an email to notify you of success or failure

In the future we would like to add support for a bunch more features including provisioning new Heroku instances and showing you the commits that will be pushed. We want to become the place to do managed deployment to Heroku. It's to easy to forget to do a backup or forget to turn on maintenance mode when deploying manually. At our day job, we have 10s of Heroku instances and being able to see the status of multiple deploys at once is going to be a major win for us.