I've been thinking about this and have an idea. Would it be possible to be able to define a password against an application that you get asked for each time to run one of the potentially damaging commands? By doing this, it means that you can easily restrict which members of the team can run those methods versus others (for instance, doing a db:pull is something which a developer might want to do, but I don't want them to db:push)
N On Sep 16, 6:13 pm, Neil <[email protected]> wrote: > Even though, I still strongly believe that there should be a "wait a > minute and think about what you're doing here" prompt at the very > least. > Yes, it's not convenient, but neither is totaling a database because > you got a bit frisky with your keyboard/muscle memory... > > Neil > > On Sep 15, 5:41 pm, Pedro Belo <[email protected]> wrote: > > > Hey guys, > > > The Heroku client gem lives here:http://github.com/heroku/heroku > > > And yes, having multiple remotes on the same git repo forces you to be > > explicit. In fact there are two ways to specify your app in this case, > > informing --app or --remote (ie heroku rake db:migrate --remote > > production). > > > Thanks, > > Pedro > > > On Tue, Sep 15, 2009 at 6:24 AM, Sarah Allen <[email protected]> wrote: > > > > It definitely makes the db commands explicit, like: > > > heroku rake db:migrate --app myapp-production > > > > Thanks for the pointer. I've written up a Pivotal Tracker chore and I > > > look forward to trying out that configuration :) > > > > On Sep 15, 2009, at 5:45 AM, Carl Fyffe wrote: > > > >> Sarah, > > > >> Here is an explanation of deploying to a production branch: > > > >>http://jqr.github.com/2009/04/25/deploying-multiple-environments-on-h... > > > >> Hope this helps! > > > >> On Tue, Sep 15, 2009 at 8:32 AM, Sarah Allen <[email protected]> > > >> wrote: > > > >>> I thought that Heroku needed the master branch. From the docs: > > >>> "Branches pushed to Heroku other than “master” will be ignored. If > > >>> you’re working out of another branch locally, you should either merge > > >>> to master before pushing, or always specify the branch name to push > > >>> to, as in “git push heroku master”. > > >>>http://docs.heroku.com/git > > > >>> I do like the idea of having a special production branch. It fits > > >>> normal development practices that I've typically done for larger > > >>> projects. I would prefer not to name it master, although I suppose > > >>> we > > >>> could move everyone to developing on "dev" or something. > > > >>> On Sep 15, 2009, at 5:11 AM, Carl Fyffe wrote: > > > >>>> I am not really a fan of the prompt idea. It seems cumbersome and > > >>>> after you have done it 83 times it won't be protection, it will be > > >>>> an > > >>>> annoyance. Just look at Windows Vista's security. > > > >>>> I *am* a fan of putting production on a different branch and > > >>>> deploying > > >>>> that. It is very similar to the force, but much more intentional. It > > >>>> has the added bonus of being a good practice. > > > >>>> I am sure there are downsides to doing it this way, but I don't see > > >>>> them at the moment. > > > >>>> On 9/15/09, Keenan Brock <[email protected]> wrote: > > > >>>>> Oops > > >>>>> Scratch previous point #1 > > > >>>>> Hmm. That is odd - I searched for heroku on github and this didn't > > >>>>> come up... > > > >>>>> --Keenan > > >>>>> On Sep 15, 2009, at 5:09 AM, Sarah Allen wrote: > > > >>>>>> Yeah, I actually totally munged the live DB right after we went > > >>>>>> live > > >>>>>> (luckily before we told anyone about the site and we had all the > > >>>>>> data > > >>>>>> backed up). I agree that some kind of are-you-sure would be the > > >>>>>> right > > >>>>>> answer. Kind of like 'rm -i' but on by default -- there could be > > >>>>>> a -f > > >>>>>> option to suppress the warning. The gem is open source... I don't > > >>>>>> know offhand how to add an interactive prompt to a rake task, > > >>>>>> but I > > >>>>>> suppose it could be added here: > > >>>>>> http://github.com/heroku/heroku/blob/master/Rakefile > > > >>>>>> I'm clearly not getting enough sleep this week, so for now I try > > >>>>>> to be > > >>>>>> quite cautious when I type heroku in particular directories, but > > >>>>>> eventually I won't be able to live with that :) > > > >>>>>> On Sep 15, 2009, at 1:45 AM, Neil wrote: > > > >>>>>>> At the very least I would expect some sort of "This is a live > > >>>>>>> environment - are you really, really sure you want to do this?" > > >>>>>>> on > > >>>>>>> the > > >>>>>>> app changing actions. (db:push, db:reset etc, similar to destroy) > > > >>>>>>> N > > > >>>>>>> On Sep 11, 3:14 pm, Carl Anderson <[email protected]> wrote: > > >>>>>>>> That was something I was wondering as well. I've literally had > > >>>>>>>> nightmares > > >>>>>>>> about doing just that (am I alone?) > > > >>>>>>>> Carl > > > >>>>>>>> On Fri, Sep 11, 2009 at 4:03 AM, Neil <[email protected]> > > >>>>>>>> wrote: > > > >>>>>>>>> I'm not sure if someone has already covered this, but although > > >>>>>>>>> there > > >>>>>>>>> are loads of really handy features in the Heroku gem, some of > > >>>>>>>>> the > > >>>>>>>>> functions that you can acheive are potentially very damaging > > >>>>>>>>> to a > > >>>>>>>>> production environment and also very easy to do. > > > >>>>>>>>> For instance, from what I've seen there is nothing to stop me > > >>>>>>>>> from > > >>>>>>>>> doing a db:push to my live application - there's no sort of > > >>>>>>>>> question > > >>>>>>>>> of confirmation etc. > > > >>>>>>>>> Is this something that's planned or is it something I've just > > >>>>>>>>> not > > >>>>>>>>> seen? > > > >>>>>>http://www.ultrasaurus.com > > > >>>http://www.ultrasaurus.com > > > >http://www.ultrasaurus.com > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
