<div class="gmail_quote">On Thu, Apr 23, 2009 at 4:09 PM, Bill Williamson <span dir="ltr"><<a href="mailto:bill@bbqninja.com">bill@bbqninja.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Fri, Apr 24, 2009 at 8:46 AM, Jim Stichnoth <span dir="ltr"><<a href="mailto:stichnot@gmail.com" target="_blank">stichnot@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there an easy, supported way to clone an existing frontend's database settings? I'm bringing up a new frontend and want it configured just like another frontend, including themes, key bindings, deinterlacers, etc.<br>
<font color="#888888">
<br>Jim<br>
</font></blockquote></div><div><br>Something I've tried... but no promises:<br><br>-Start old frontend (that you want to clone)<br>-Go into settings, give it a custom identifier of "new-frontend" (or whatever)<br>
-Quit<br>-Start old frontend<br>-Go into settings, change custom identifier back to no (blank/unchecked/whatever it is)<br>-Start new frontend, but on first start put in that same custom identifier ("new-frontend")<br>
<br><br>That seemed to work for most things. When you change the name to a new one it does a copy of all settings on quit. When you bring up the new one yo can then use those settings. <br></div></div></blockquote><div>
<br>Thanks. This sounds like an excellent approach -- no messing around with the database in an "unsupported" fashion. I didn't know about the custom identifier setting before, which I guess simply overrides the hostname in the database.<br>
<br>Just to complete my understanding, it seems that settings for old frontends will stick around in the database forever and never be cleaned out. Is that the case?<br><br>Jim <br></div></div>