![cdn-starter-1ee package icon](/_next/image?url=https%3A%2F%2Fcdn.wasmer.io%2FCACHE%2Fimages%2Ficon%2Fpackage%2Fbc52b5c8-b0c0-44a1-8c20-5f7322f70b87_default_icon%2F7f4e110452386f9f0d31ad0c47db7392.png&w=96&q=75)
![cdn-starter-1ee package icon](/_next/image?url=https%3A%2F%2Fcdn.wasmer.io%2FCACHE%2Fimages%2Ficon%2Fpackage%2Fbc52b5c8-b0c0-44a1-8c20-5f7322f70b87_default_icon%2F7f4e110452386f9f0d31ad0c47db7392.png&w=96&q=75)
A CDN starter template using Static Web Server.
You can follow the full tutorial from here
Usage
All the static files will be served from the public
folder, and the static webserver will be configured using the config.toml
file.
You can run the CDN template easily using Wasmer (check out the install guide):
wasmer run microchipgnu/cdn-starter-1ee --net
[!TIP] You can also run
wasmer run . --net
in the root of this repo, after runningnpm run build
Open http://localhost:8080 with your browser to see the CDN.
Deploy on Wasmer Edge
The easiest way to serve your public assets is to use the Wasmer Edge as your CDN.
Live example: https://microchipgnu-cdn-starter-1ee.wasmer.app/
Run this commmand to deploy to Wasmer Edge:
wasmer deploy
[!NOTE] You will need to change the namespace in
wasmer.toml
to your own namespace and app name inapp.yaml
to your own app name.