Support of remote templates is the major feature of the 0.5 release.
Keep in mind that the current "remote templates" implementation is
experimental. It is quite slow and greedy. The scope of this 0.5 release was
to publish a proof of concept. We are planning some improvements related to
performance and scalability in next releases.
That said, let's give it a try!
We can use diecutter.io to render the template:
$ curl -X POST --data name=Novapost http://diecutter.io/github/novagile/diecutter/0.5/demo/templates/greetings.txt
Of course, you can also render directories as archives:
$ curl -X POST -d django_project=wonderful http://diecutter.io/github/novagile/diecutter/0.5/demo/templates/+django_project+/ | tar -zt
Supported URLs are http://diecutter.io/github/<owner>/<project>/<revision>/<path/to/file/or/directory>,
- <owner> is the repository owner, "novagile" in the examples above.
- <project> is the repository name, "diecutter" in the examples above.
- <revision> is the commit, tag or branch, "0.5" in the examples above.
- <path/to/file/or/directory> is the path to the file or directory template
in the repository, "demo/templates/greetings.txt" in the first example above.
Yes, that's all.
Why does it matter?
Remote templates feature makes diecutter.io a SAAS: you can use diecutter.io
service to render templates that are managed in online public repositories.
The templates does not belong to diecutter. You, or third-party authors, own
Now, let's share templates online!