We should at least fix the launcher case, which should be easy. We can special-case that, detecting we're a launcher config and changing the automatic config it builds at startup to use the old db names.
On Thu, Jan 4, 2018 at 7:47 AM, Mathieu Lonjaret <[email protected] > wrote: > Hi, > > as of rev 7eda9fd5027fda88166d6c03b6490cffbf2de5fb > (https://github.com/camlistore/camlistore/commit/ > 7eda9fd5027fda88166d6c03b6490cffbf2de5fb), > the default names of the various databases used by Perkeep change. > That basically means: > > 1) if you were using dbNames (not dbname), to set your "index" > database name, then it concerns you. > 2) if you were using dbNames for the other "secondary" indexes and > queues then your are affected, but it's maybe not as important. > 3) If you are running a Camli/Perkeep instance on GCE, deployed with > the launcher, you fall into case 1) (and case 2) as well). > > We probably need to think about a transition patch to help users > migrate at least their index database, or at the very least warn them. > > But to figure out how much effort we have to put into this, it would > help to know how many among you are affected. > > So, if you are either running Perkeep in production with a DBMS > (MySQL, PostgreSQL, MongoDB), or running an instance from the GCE > launcher, could you please let us know? > > Feel free to forward this to friends who are not on the mailing-list too. > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
