[opencms-dev] replicating openCMS instances
Marcus Popetz
marcus at roundpeg.com
Tue Oct 31 16:38:07 CET 2006
You could give it a bogus db name, let it create the tables and
install the modules, and then switch the db name in the config files
after you're done installing.
-mp
On 10/31/06, Felix Sprick <felix.sprick at netlight.se> wrote:
>
>
>
>
> HI guys,
>
>
>
> I am trying to run my openCMS-built website in multiple instances behind a
> load-balancer. Since I am running openCMS with mysql I thought it would be a
> good idea to use mysql's replication functionality to have several instances
> of the database. What I did was
>
>
>
> creating database1 on server1
> setting up openCMS on server1 using database1
> creating content of website in openCMS instance1
> replicating database to server2
> setting up second instance of openCMS on server2 and connecting that one to
> the replicated database
>
>
>
> It works quite fine, but I get a warning when running the setup wizard
> saying that if I don't create the database tables, I can't import modules
> and stuff. But I don't want to create new tables since they are already
> existent through the replication. So I ignored that warning and finished the
> installation. After that I could log into the openCMS system, but the
> display was scrambled because lots of resources were missing.
>
>
>
> Any ideas how to fix that or solve this issue in another way?
>
>
>
> Thanks,
>
> Felix
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
More information about the opencms-dev
mailing list