On 6 July 2010 13:18, Andy Jeffries <a...@andyjeffries.co.uk> wrote: > On 6 July 2010 11:31, Michael Pavling <pavl...@gmail.com> wrote: >> >> On 6 July 2010 11:19, Andy Jeffries <a...@andyjeffries.co.uk> wrote: >> > You can do this (I've had to do it for a client) but it's not simple >> > <snip super secret process> >> >> Very interesting approach. Will file that for future reference. > > I hope you never need it :-) > >> >> > The last step, if you're using Passenger ensure that the last child is >> > never >> > killed off (if it is, it will lose the decryption key which is now only >> > in >> > memory). I can't remember the setting but there's a timeout setting >> > which >> > you can set to zero so the last child never dies. >> >> Hope you've got good UPS and redundancy too (and a well-negotiated >> call-out fee to re-encrypt everything if the YTS boy unplugs the power >> :-) > > We're developing the site but the day to day running is down the client (but > they have lots of power from various sources, redundancy and sysadmins to > type the password back in).
Is the client trying to keep the code hidden from his own sysadmins or are you trying to hide it from the client? Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
