So now and then, it is claimed that MageBridge is slow. It combines Joomla! and Magento into one webapplication, so it must be slower than Magento standalone. In many cases, these conclusions are based on personal feelings and not solid facts. This whitepaper tells you how to gather the facts, and get a clear view on what is causing what to perform how.

Read more: Benchmarking MageBridge performance

TurnKey Linux offers various images for use in popular virtualization tools like VMware and VirtualBox. We have taken one of these images, and optimized it for MageBridge. This allows you to quickly setup a MageBridge site (running both Joomla! as Magento) for testing purposes. This tutorial tells you how to get started with this appliance. Note that we do not recommend to use this appliance in production environments.

Read more: Using the MageBridge-optimized TurnKey image

While you should enable Magento caching at all production sites, the caching ability of MageBridge can give your site even more performance. However, this performance gain is not as straightforward as caching in Magento. This whitepaper gives you more details.

Read more: MageBridge caching

With MageBridge, we always recommend to use two separate VirtualHosts for Magento and Joomla! - this guarantees optimal performance and security. But because each VirtualHost also uses a separate domain, this would require you to purchase two SSL-certificates as well. To bypass this problem, you could try to remove the Magento URL from each MageBridge page. This tutorial explains how to do this.

Read more: Two VirtualHosts but one domain

When you move a MageBridge environment to another server, there are various things you need to do to get things working again. In general, you are moving a Joomla! application and a Magento application - which should be copied as you normally would. MageBridge only brings in one database table that needs changing.

Read more: Moving a MageBridge site

MageBridge relies on the correct setup of file-permissions within both Joomla! as Magento. If file-permissions are not setup correctly, the upgrade of MageBridge will fail. This document helps you analyze this problem. Please note that if the hosting environment is not correctly setup, we will be unable to support MageBridge.

Read more: File permissions for MageBridge

Duplicate content is regarded by many bad for search engine optimization. Though it could be argued whether this is needed or not, you might be tempted to make the Magento webshop only accessible through Joomla! and not any more by accessing the Magento application directly. While MageBridge translates every single Magento-link to a MageBridge link, visitors can still visit the Magento application if they would know the direct URL. Because MageBridge serves the same content as Magento does, this is duplicate content. And if visitors can access Magento directly, there is a (very small) chance search engines will find out about this as well.

Read more: Prevent direct access to Magento using htaccess

Setting up a website with both Magento as Joomla!, can not only be more than a days job - it can also introduce new security risks. Primarily, the risks in one application (Magento or Joomla!) could endanger the application. Here we discuss which security measures could (or should) be taken in both Joomla! as Magento to secure the lot.

Read more: MageBridge Security Guide