The Fission CLI has the following commands:
Details on all of these commands can be seen at any time by running
Usage: fission [--version] [--help] COMMANDFission makes developing, deploying, updating and iterating on webapplications quick and easy.Available options:--version Show version--help Show this help textAvailable commands:login Add your Fission credentialslogout Logout of your Fission accountregister Register for Fission and loginreset-password Reset Fission Passwordup Keep your current working directory updown Pull a ipfs or ipns object down to your systemwatch Keep your working directory in sync with the IPFSnetworkwhoami Check the current user
Before using Fission services, you need to login.
register prompt you for user credentials and store them in
If you ever need to log into a different account, just delete
~/.fission.yaml and login again.
This is the only command you need to get your content hosted on the decentralized web!
up, make sure that you:
have an IPFS daemon running in the background (through ipfs-desktop, or in another terminal)
are currently in the directory containing the assets you want to deploy
A few things happen when you run
the directory is recursively added to IPFS through your local node (the equivalent of running
ipfs add -r ./)
Your local node connects to a remote Fission node (the equivalent of running
ipfs swarm connect [peerId])
A Pin Request is sent to our server which tells the remote Fission node to get and store the requested content directly from your local node
a request is sent to our server to update the Domain associated with you account to point to the new content using dnslink ℹ
[username].demo.runfission.com at our IPFS gateway (ipfs.runfission.com)
_dnslink.[username].demo.runfission.com at your uploaded content
Note: It may take some time for DNS to propagate. So give it a minute or two if it doesn't load immediately.
But from your perspective, it's just success messages, emojis, and a link to your hosted website 🚀
If you're currently developing your website and want continuous updates to the hosted version, use
watch instead of
This command does the same thing as
up but after uploading your content, it continues watching the current directory for changes. Every time you change a file, it adds the new content to IPFS, pins it to the remote Fission node, and updates DNS.
There are a few advanced settings and configuration that can be set by your local environment.
To get more details on what's happening, you can turn DEBUG to true like so:
DEBUG=true fission up
By default, the fission-cli assumes that IPFS is installed at
/usr/local/bin. You can call the CLI with a custom setting or permanently set a shell variable:
IPFS_PATH=/Snap/ipfs fission up