MJML CDN gateway API

[timkelty]

Rather than installing installing node/MJML CLI as a runtime dependency, we could offer this an API from our gateway, allowing projects to make requests and do whatever they wish with the output.

[jamesmacwhite]

100% yes! We currently the use the MJML API because we weren't sure about the binary availability under serverless, but it bothers me as there is no SLA or support for the API, so transitioning from it would be ideal

[jamesmacwhite]

Is it possible to use the MJML CLI with Craft Cloud? I figured it wouldn't be possible, given the serverless nature and deployment process.

Can you reference the binary under /var/task?

[timkelty]

If committed the binary to the repo, you could reference it, but I'm pretty sure MJML is going to need node.js in the runtime env to run, and it wont be there (it is only in the build).

If you mean in the build process, then yes – you should be able to just include it as a dependency and run it via npm build (npm-script)

[jamesmacwhite]

If committed the binary to the repo, you could reference it, but I'm pretty sure MJML is going to need node.js in the runtime env to run, and it wont be there (it is only in the build).

If you mean in the build process, then yes – you should be able to just include it as a dependency and run it via npm build (npm-script)

That's what I thought, the MJML plugin for Craft, does the compiling for you, but relies on node being available. I use the MJML API under Craft Cloud and the CLI locally. If there was an API offered through Craft Cloud it would make me much happier as using the MJML API has no SLA or guarantees so it's a bit of a risk generally, e.g. if it goes away, breaks etc.

Alternative is compiling the templates through the build command and then pointing things to that instead, but that would make using the MJML Craft plugin slightly redundant.