Configuring CUE
CUE configuration involves configuring CUE itself, and also configuring the nginx web server that serves the CUE application.
The actual
CUE
configuration consists of editing YAML format configuration files,
identified by the file type extension .yml
. The
delivered system includes a number of such configuration files containing
CUE's
default configuration settings. These files are located in the
/etc/escenic/cue-web-2.9.7-6/
folder. If your
CUE
installation includes any extensions, these extensions may have their own
configurations stored in other locations.
The
/etc/escenic/cue-web-2.9.7-6/
folder also contains a file called config.yml.template
,
containing the property settings that you always need to set when
installing CUE.
To use this file you rename it to config.yml
and then
edit the contents.
To configure CUE:
-
If necessary, switch user to
root
.$
sudo su -
Copy
/etc/escenic/cue-web-2.9/config.yml.template
toconfig.yml
:#
cp/etc/escenic/cue-web-2.9/config.yml.template
/etc/escenic/cue-web-2.9/config.yml
-
Open the new
/etc/escenic/cue-web-2.9/config.yml
for editing. For example#
nano /etc/escenic/cue-web-2.9/config.yml -
Uncomment and set the required endpoint parameters (which you will find at the top of the file):
endpoints: escenic: "http://escenic-host:81/webservice/index.xml" newsgate: "http://newsgate-host/newsgate-cf/"
where:
-
escenic-host is the IP address or host name of the Content Engine CUE is to provide access to
-
newsgate-host is the IP address or host name of the CCI Newsgate system CUE is to provide access to. If no CCI Newsgate system is present, then do not uncomment the
newsgate:
line.
-
-
If your CUE configuration makes use of an Escenic-CCI Newsgate bridge, then you will need to add a third line under
endpoints
:endpoints: escenic: "http://escenic-host:81/webservice/index.xml" newsgate: "http://newsgate-host/newsgate-cf/" bridge: "http://bridge-host:7001/ngece-bridge/"
where bridge-host is the IP address or host name of an Escenic-CCI Newsgate bridge. (A bridge is a service capable of converting Escenic content to Newsgate format, and is required to support Newsgate write-to-fit functionality in CUE.)
-
Save the file.
-
Enter:
#
dpkg-reconfigure cue-web-2.9This reconfigures CUE with the Content Engine web service URL you specified in step 3.
-
Open
/etc/nginx/sites-available/default
for editing, and replace the entire contents of the file with the following:server { listen 81 default; include /etc/nginx/default-site/*.conf; }
-
Create a new folder to contain your site definitions:
#
mkdir /etc/nginx/default-site/ -
Add three files to the new
/etc/nginx/default-site/
folder, calledcue-web.conf
andwebservice.conf
:#
touch /etc/nginx/default-site/cue-web.conf#
touch /etc/nginx/default-site/webservice.confa#
touch /etc/nginx/conf.d/request-entity-size-limit.conf -
Open
/etc/nginx/default-site/cue-web.conf
for editing and add the following contents:location /cue-web/ { alias /var/www/html/cue-web/; expires modified +310s; }
Depending on the version of nginx that you have installed, the alias specified in
cue-web.conf
may need to be set to/var/www/cue-web/
instead of/var/www/html/cue-web/
. -
Open
/etc/nginx/default-site/webservice.conf
for editing and add the contents described in Web Service CORS Configuration. -
Open
/etc/nginx/conf.d/request-entity-size-limit.conf
for editing and add the following contents:# Disable default 1Mb limit of PUT and POST requests. client_max_body_size 0;
(If you do not add this setting, then nginx will not allow larger files such as images and videos to be uploaded to CUE.)
You should now be able to access
CUE by
opening a browser and going to
http://
host:81/cue-web
.