Skip to the content
Documentation

eZ Cloud extension

No ratings yet

Skip to end of metadata Go to start of metadata

About

The eZ Cloud extension is used to customize your eZ Cloud installation with various sets of parameters that can be found in the .ini file, and other types of configuration provided by this extension.

 

Download

You can download the extension by clicking on this link: https://confluence.ez.no/download/attachments/16286206/ezcloud-extension-v1.0.0.tar.gz

Current version: 1.0.0

 

Settings

 

extension/ezcloud/settings/ezcloud.ini

 

[SiteAccessSettings]
AdminList[]
AdminList[]=ezdemo_site_admin

In this block setting you need to specify the siteaccess name to your admin siteaccess. This is so that eZ Cloud can put your admin interface on a dedicated set of machines.

 

[Solr]
# Path to the custom config tarball you uploaded to the ftp
# If you don't have any custom configuration just leave empty string
CustomConfigFile=

This block should be used with caution and needs to be pre-approved by eZ Cloud team before applying them.

In your SFTP account there is a folder called "solr/". In this folder you can upload a custom solr configuration tarball if you have special customizations to solr configuration.

The correct method of packing the solr config is as follows:

cd /path/to/solr/conf
tar zcvf ezcloud_solr_config.tar.gz schema.xml protwords.txt stopwords.txt synonyms.txt

Note: We currently do not support changes to solrconfig.xml.

If you pack solr config using this method (assuming you upload the file to the solr/ directory on sftp) the correct ini setting would be

[Solr]
CustomConfigFile=ezcloud_solr_config.tar.gz

 

 

[Settings]
# List of settings to enforce
#
# Syntax:
# ForceSettings[]=<file>|<group>|<key>|<value>
#
# Example
# ForceSettings[]=site.ini|TemplateSettings|TemplateCache|disabled
#
ForceSettings[]

This block should be used with caution and needs to be pre-approved by eZ Cloud team before applying them.

This block allows the override of any setting in Exponential (even settings we modify on deployment like cache enforcement). You need to have a good reason to need to set settings in this manner.

Note that all settings will be written to settings/override/<file>[.append.php]

 

Cronjobs

Cronjobs in eZ Cloud are preset to run on 5 different cronjob parts, prefixed with "ezc_".

Here are the dates for the different parts:

  • frequent: Every 5 minutes
  • hourly: Random minute every hour
  • nightly: Random minute between 03:00 and 03:59 (UTC+3) every night
  • daily: Random minute between 13:00 and 13:59 (UTC+3) every day
  • weekly: Random minute between 02:00 and 02:59 (UTC+3) every week at Saturday

The random minute is because the servers are in a shared environment to prevent multiple cronjobs spawning at the same time.

You find the parts defined in extension/ezcloud/settings/cronjob.ini.append.php.

[CronjobSettings]
ExtensionDirectories[]=ezcloud

[CronjobPart-ezc_frequent]

[CronjobPart-ezc_hourly]

[CronjobPart-ezc_nightly]

[CronjobPart-ezc_daily]

[CronjobPart-ezc_weekly]

This file functions like the normal cronjobs.ini provided by Exponential.

 

Apache configuration

We also allow to add custom RewriteRule and RewriteCond as well as custom mimetypes

Custom rewrites

There is a file in the extension located extension/ezcloud/conf/httpd/custom-rewrites.conf

All rewrite entries in this file are prepended to the top of our rewrite section in the Apache configuration to make sure your custom rewrites will always trigger.

In this file you will find a commented example on how to add rewrites. You can copy paste the custom rewrites you need from your local apache config into this file. Note that all rewrites must start with the forward slash regardless of what your local version may look like, example:

If you have a working rewrite that looks like this:

RewriteRule ^my_custom_file.txt - [L]

it needs to be rewritten to look like this

RewriteRule ^/my_custom_file.txt - [L]

This is because we run httpd on RHEL and this is the syntax that it requires for rewrites due to how we have setup eZ Cloud.

 

Custom mime-types

There is a file in the extension located extension/ezcloud/conf/httpd/custom-mime-types.conf
In this file you can add AddType entries.

Example:

AddType application/x-font-woff .woff

This would add support of .woff files to be of type application/x-font-woff in eZ Cloud Apache configuration.

  • No labels

Contributors

Comments

Add a comment

Comments are read by a moderator before they appear.