What would you hold up as an example of a powerful web app with significant usage?
Google Docs suite perhaps?
HN user
[ my public key: https://keybase.io/odin; my proof: https://keybase.io/odin/sigs/8r421QEKM378bhxKXl5WvZeZuq0qY2je-5dv3-tk2yw ]
What would you hold up as an example of a powerful web app with significant usage?
Google Docs suite perhaps?
Sure. This is intended as a quick way to send small bits of sensitive information over email, chat, etc.
> 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
Sadface. http://rubyjs.org/buy.html
Looks good, it would be cool if you added some sort of proper ranking for certain games. Something similar to ELO where everyone is ranked and you win more points by beating someone that is ranked higher.
Thanks for the feedback. We should have done this a while ago. It's easy to forget that other people have no idea what we are building. Cheers.
https://github.com/freshshell/fresh/commit/4ebf599aa61b54b66... and https://github.com/freshshell/fresh/commit/000d7ce00b9029881...
Fresh handles local files too: https://github.com/twe4ked/dotfiles/blob/master/config/fresh...
Absolutely. This is on the road map (https://github.com/freshshell/fresh/issues/11). At the moment running `fresh update` is the only way to update the source repos. I realise this isn't ideal, but we never update repos without you knowing.
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.
Here's my `.freshrc` for examples of how you can use fresh. https://github.com/twe4ked/dotfiles/blob/master/config/fresh...
Just mounted a TV on the wall at the office for a dashboard yesterday. Perfect timing!
We're planning on having options for things like maintenance mode on a per deploy basis with project defaults. We're also looking into supporting the Heroku preboot labs feature.
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.
Yeah, we will try to get a screen cast out soon. We didn't spend to much on the marketing side of things.
“Movement saved: 242,553 pixels”.