$response->headers->set( "Content-Security-Policy", "default-src 'self'; style-src 'self' 'unsafe-inline'"; $response->headers->set( "X-Content-Security-Policy", "default-src 'self'; style-src 'self' 'unsafe-inline'"; $response->headers->set( "X-Webkit-CSP", "default-src 'self'; style-src 'self' 'unsafe-inline'";
If you are using a different domain for serving static content, you have to add this domain to the
The Aimeos web shop is able to use different databases for its data domains. Thus, you can configure a separate database e.g. for all customer or order related data. If no specific database is configured for a data domain, the default database will be used.
The default database configuration is defined in the
./Resources/config/config.yml file of the Aimeos shop bundle and looks like
aimeos_shop: resource: db: adapter: mysql host: %database_host% port: %database_port% database: %database_name% username: %database_user% password: %database_password% stmt: ["SET NAMES 'utf8'; SET SESSION sql_mode='ANSI'; SET SESSION sort_buffer_size=2097144; SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;"] limit: 2 opt-persistent: 0
It defines the database location and credentials as well as the default statements that are executed when opening a connection ("stmt"), the maximum allowed connections to this database for the request ("limit") and if the database connection should persist between connections ("opt-persistent"). You can define one database for each domain (e.g. order, customer, etc.) in the same way. To store all orders in a separate database, add another configuration block to your
aimeos_shop: resource: db-order: adapter: mysql host: '<hostname or IP address>' port: '<server port>' database: '<database name>' username: '<database user>' password: '<user password>' stmt: ["SET NAMES 'utf8'; SET SESSION sql_mode='ANSI'; SET SESSION sort_buffer_size=2097144; SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;"] limit: 2 opt-persistent: 0
The important line contains the
db-order key, which tells Aimeos that this resource configuration is for a database that should contain all data from the "order" domain (which includes all mshop_order tables).
A big performance boost can be achieved by installing
APCu (the APC user cache). It can cache all configuration and translation entries in the shared memory of the web server which can improve performance by 50%.
Be aware that you have to clear the APC user cache manually each time after you've changed a configuration option or a translation!
In order to tell your application to use the APC user cache, you need to change the
apc_enabled setting in the
./config/shop.php file of your application:
aimeos_shop: apc_enable: true apc_prefix: 'symfony:'
If you have more than one shop application on the same server, you must assign an unique apc_prefix for each instance!
During development it's very useful to disable the internal content caching done by the Aimeos package. By default, the following output is cached:
- HTML header and body of each component by the Aimeos caching framework
- Small basket and last seen products in the session of the user
Thus, new content is only generated if you flush the caches and/or delete the frontend cookie in your browser.
To disable the content caching completely, add this to your
aimeos_shop: madmin: cache: manager: name: None
Don't disable the content caching by default in production environments. This has a severe performance impact!
The basket is also updated automatically if you add products to or delete products from the basket resp. modifying the basket content in another way.
You can also disable caching the basket content in the sessions for development using the client/html/basket/cache/enable configuration option.
The content cache is usually enabled by default if you haven't disabled it during development in your
If you have a high volume of products (50k+) and your database server gets slower due to the amount of queries executed, you can offload the content cache entries either to another database server or to an in-memory key/value store like Redis.
To move the content cache entries to a Redis server, you have to install the ai-cache extension. The extension contains documentation how to configure your application for Redis support.
Alternatively, you can move the cached component content to another database server. In this case, you must add a
db-cache resource block to your
resource: db-cache: adapter: mysql host: '...' port: '...' database: '...' username: '...' password: '...' stmt: ["SET NAMES 'utf8'", "SET SESSION sql_mode='ANSI'"] limit: 2 opt-persistent: 0
Distribute static files#
Browsers don't load all required files at once referenced inside a HTML document. Instead, they limit the number of concurrent requests for a single domain. To get around this, a common way is to make the files also available via a different domain, so the browsers will download more files in parallel. Thus, rendering the page is much faster for the user.
One way is to create a second virtual host configuration in your web server which uses a sub-domain like "static.example.com". The document root should point to the same directory as your main virtual host (e.g. example.com) in the file system to ease maintenance. Otherwise you would have to make sure that the files are in sync in both directories.
If the internet connection to your customers is short and fast and your server is able to handle the load, this way is the preferred one - especially, if you are able to serve the files from a memory-based cache like a reverse Nginx proxy or Varnish.
Another option is to use a domain from a content delivery network (CDN) like Amazon Cloudfront. Usually, you can configure these services to retrieve the static files on the first request from your host and deliver them from their caches afterwards.
The advantage of a CDN over a sub-domain on your own server is the load-balancing across many servers and the distribution from a server near to the visitors of your web site. Both can improve the speed of your web site a lot.
In both cases, you need to configure the Aimeos Symfony bundle to create links to the product pictures with a different domain. This can be done via an entry in the
aimeos_shop: resource: fs: baseurl: "https://static.example.com/media/"
The value in baseurl must be the URL prefix where the sub-directories for the product pictures and all related files are available.
You can also use the "aimeos/ai-filesystem" package to store files directly on another server. There are drivers for different services available and for details, please have a look at the readme file of the ai-filesystem package. An example configuration for using an Amazon S3 storage would be:
aimeos_shop: resource: fs: adapter: FlyAwsS3 credentials: key: 'your-key' secret: 'your-secret' region: 'your-region' version: 'latest' bucket: 'your-bucket-name' prefix: 'your-prefix' baseurl: 'https://your-bucket-name.s3.your-region.amazonaws.com/your-prefix/'