Fission makes it easy to build and host web apps using only frontend and local development tools with no effort put into servers or deployment workflows.
In this guide, we will use the Fission CLI to publish the
elm-pages-starter to the web.
elm-pages-starter to your local development environment.
git clone [email protected]:dillonkearns/elm-pages-starter.git
Install and build the app.
cd elm-pages-starternpm installnpm run build
elm-pages-starter is built, we are ready to publish it with Fission.
Initialize the project as a Fission app with
fission app register. You will be prompted for a build directory.
$ fission app register👷 Build directory (./dist):
dist as your build directory, and
fission will initialize your app.
✅ App initialized as long-skinny-stone-monkey.fission.app⏯️ Next run fission app publish or fission app publish --watch to sync data💁 It may take DNS time to propagate this initial setup globally. In this case,you can always view your app athttps://ipfs.runfission.com/ipns/long-skinny-stone-monkey.fission.app
Fission has created a
fission.yaml file with your app configuration.
fission.yamlignore: url: long-skinny-stone-monkey.fission.appbuild: ./dist
url is where the app will be on the web after it has been published,
build tells the fission which directory to publish, and
ignore is a list of files and directories to ignore. See the Fission YAML guide for more details.
fission app publish to publish the webpage.
$ fission app publish🚀 Now live on the network📝 DNS updated! Check out your site at:🔗 long-skinny-stone-monkey.fission.app
Copy the URL into your browser and you will see the
elm-pages-starter live on the web!
You can continuously update the hosted version of the app by running
fission app publish --watch. Fission will watch the files in
dist and publish when changes occur.
We have put the
elm-pages-starter out on the web without setting up a DevOps environment or going through a complex deployment workflow!
At this point your mind might be swimming with a thousand questions. Here are a couple of resources that explain how this all works:
WebNative: How to put a full stack directly in the browser talk at Speakeasy JS
In the next section, we will add Fission auth to the