Update README.md

Author: erikap

README.md

@@ -1,10 +1,22 @@
-Export JS Template
-==================
+Export service
+==============
 
 Microservice to export data using custom defined SPARQL queries.
 
 ## Using the template
-Run the `semtech/mu-export-js-template` service and mount an export configuration in `/config/export.js`.
+Extend `semtech/mu-export-service` service and add an export configuration in `/config/export.js`.
+
+## Example Dockerfile
+
+```
+FROM semtech/mu-export-service:0.3.0
+MAINTAINER Erika Pauwels <erika.pauwels@gmail.com>
+
+COPY export.js /config/export.js
+
+```
+
+## Export configuration
 
 The `export.js` file defines an array of export configuration objects as follows:
 
@@ -27,27 +39,12 @@ An export configuration object consists of the following properties:
 * [REQUIRED] `query`: the SPARQL query to execute. This may be a `SELECT` or a `CONSTRUCT` query.
 * [OPTIONAL] `file`: name of the downloaded file. The filename may also be provided through a query param on the export request (e.g. `/example?file=my-name.csv`). If no filename is provided, the export will be displayed inline in the browser.
 
-## Example docker-compose
-
-```yaml
-version: '2',
-services:
-  export:
-    image: semtech/mu-export-js-template:0.2.0
-    volumes:
-      - ./:/config
-    links:
-      - database:database
-```
-
-Note: if you extend the `semtech/mu-export-js-template` with an `export.js` file instead of mounting a volume in `/config`, the `ONBUILD` commands of the `semtech/mu-javascript-template` will not be executed in your image since `ONBUILD` is only executed one level deep.
-
 ## Using variables in the export query
 You can also define variables in your SPARQL export query which will be replaced with query param values at runtime. Therefore, we use [ES6's tagged template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#Tagged_template_literals).
 
-Import the `template` tag function from `/app/template.js` in your `export.js` and apply the tag function on your query. You can then define variables in your SPARQL query using `${'myVariable'}`. At runtime the variable will be replaced with the value provided in the `myVariable` query param of the request.
+Import the `template` tag function from `/app/template.js` in your `export.js` and apply the tag function on your query. You can then define variables in your SPARQL query using `${'myVariable'}` (note the quotes around the variable name). At runtime the variable will be replaced with the value provided in the `myVariable` query param of the request.
 
-An example `export.js` file may look as follows:
+An example `export.js` including variables file may look as follows:
 
 ```javascript
 import template from '/app/template.js';
@@ -65,3 +62,17 @@ export default [
 ```
 
 A GET request on `/example?class=<http://xmlns.com/foaf/0.1/Person>` will export the first 100 URIs of type `foaf:Person`.
+
+## Example docker-compose
+If you don't want to build a new Docker image you can also run `semtech/mu-export-service` and mount your export configuration in `/config`.
+
+```yaml
+version: '2',
+services:
+  export:
+    image: semtech/mu-export-service:0.3.0
+    volumes:
+      - ./:/config
+    links:
+      - database:database
+```