This is how to describe the process of adding a template to be used by a service. To illustrate the process this tutorial adds an index.html file for our html5as service to provide.

Here is the commit introducing this functionality to html5as Software release: commit diff.

You can access the Theia using the url and logging in with username and password.

Create index.html.in in slapos/software/html5as-base/templates/ directory by right-clicking templates and selecting New File.

Open index.html.in and copy the script into it:

{% if title %}
<h1>{{ title }}</h1>
{% endif %}
<p>Hello World</p>

Add [template_index_html] section into software.cfg:

[template_index_html]
recipe = slapos.recipe.build:download
url = ${:_profile_base_location_}/${:_update_hash_filename_}
_update_hash_filename_ = templates/index.html.in
md5sum = d57cb01df5941e139b02a2f7bdabcdc8

Make sure the md5sum is correct by running:

$ cd ~/srv/project/slapos/software/html5as-base/
$ md5sum templates/index.html.in

Note : There is no difference between your md5sum here and the tutorial. It has to be the same. 

Add context key in [template-cfg]

[template-cfg]
context =
  ...
  key template_index_html_target template_index_html:target

Add it in profile [profile-common] section

[profile-common]
...
template_index_html = {{ template_index_html_target }}

This file is responsible to render the instance file. So it needs to have the path of the index.html.in template.

Simple command to put default index.html content in the docroot: 

[downloader]
recipe = plone.recipe.command
command = rm -r ${html5as:docroot}/*; cp ${default_index_html:rendered} ${html5as:docroot}/

[default_index_html]
recipe = slapos.recipe.template:jinja2
template = {{ parameter_list['template_index_html'] }}
rendered = ${directory:srv}/index.html
title = {{ parameter_dict['title'] }}
context =
  key title :title

A new section [default_index_html] is added to render the template. It gets the path of the template by being rendered by instance.cfg.in which got its path from software.cfg.

The template is being rendered with the context key title taken from the parameter title.

Run the command:

$ cd ~/srv/project/slapos/software/html5as-base/
$ md5sum instance_html5as.cfg.in

Copy the result in the md5sum key of [instance_html5as] section of software.cfg

Note :

The displayed MD5 checksum might differ from yours, but this is not a concern. The MD5 checksums for the remaining content on this page may vary, but it's important that only the first one is identical.

Run the command:

$ cd ~/srv/project/slapos/software/html5as-base/
$ md5sum instance.cfg.in

Copy the result in the md5sum key of [template-cfg] section of software.cfg

slapos node software and slapos node instance are the commands for compiling and instantiating. Before instantiating please make sure that the compilation is completed.

Verify the output of 

$ slapos node software --all
$ slapos node instance --all

to make sure the compiling and instantiating are completed.

Before instantiating please ensure that the compilation is completed.

Call the request script to capture the connection parameters:

$ cd ~/srv/project/slapos/software/html5as-base/
$ bash ../../../request-html5as-base.sh 

Then you can verify the index template from server_url by

$ curl your_server_url

Use the link displayed instead of "your_server_url"

As long as you see the title parameter passed from the request script on the output of curl, it means the new template is taken into account.