This standalone service exposes the functionality of converting and html file into icml. The API offered is as follows:

• POST /api/auth
• POST /api/htmlToICML

1. As this service is meant to be from many clients, the first endpoint allows clients to acquire their access tokens in order to be able to use the service*. A call to the api/auth endpoint considered valid if it contains the Authorization header with value Basic base64encoded(clientId:clientSecret).
   The response of a valid call to the api/auth will return an accessToken** (JWT)
2. A call to the api/htmlToICML in order to be considered valid should have the Authorization property in its headers with value Bearer <the value of an accessToken provided by this service>. The property Content-Type should be multipart/form-data and finally the body should contain the actual HTML file under a form field called html.
   The response of this endpoint will be a file stream or a JSON object when an error occurred

*client's registration required beforehand
**the life span of an accessToken is 8 hours

The service is fully dockerized for ease of use for either development or for use in production.

In the root of the service run docker-compose up
This container includes the actual service as well as a Postgres DB

In the root of the service run docker-compose -f docker-compose.production.yml up This container contains just the service. An external Postgres DB should be provided.

PUBSWEET_SECRET
SERVER_PORT
SERVER_HOST
SERVER_PROTOCOL
POSTGRES_USER
POSTGRES_PASSWORD
POSTGRES_HOST
POSTGRES_DB
POSTGRES_PORT
NODE_ENV=production

All the above are required

When the service is up by executing docker exec -it <name_of_the_icml_server_container> yarn create:client.
The above will produce a valid pair of clientId and clientSecret