To get started deploying a site on Skynet, create a folder with an
This works for static sites, along with client-side rendered Single Page Applications. Check out our Skynet Introduction Workshop for a more in-depth walkthrough.
Official Documentation and SDKs
Skynet SDK Docs – Documentation for all the SDKs
Load skynet-js Gist –Code snippet for loading
skynet-js in browser, without build tools and without relying on a specific portal.
SkyDeploy – Command-Line Tool for easily deploying web apps on Skynet and setting the skyns records to point your HNS domain to the new version
Upload2Cloud – Windows Explorer integration for sending files and directories to Skynet. Python script available.
Vue CLI Deployment Plugin – Vue UI based tool for site upload with auto Namebase/Handshake updates
Skynet SDK for Dart – Fully-featured Skynet and MySky SDK for use in Dart and Flutter projects
py-skydb – Python Wrapper that you can use to interact with SkyDB
skynet-swift – Swift SDK for uploads, download, registry and SkyDB
ruby-skynet – Ruby SDK for uploads and downloads
Skystandards – A proposal for data standards to be adopted in Skynet applications in such a way that users can share and use their data in different Skynet apps
If your website is structured to be client-side, then hosting it on Skynet is straightforward. If not, it is likely your website will need to reconsider some parts of its architecture to be fully-functional on Skynet.
Many of these will be incorporated into our Developer Guides, but in the meantime, some things to keep in mind:
For skapps, it's best to use and link URLs that are a subdomain of the portal domain. That means either using an HNS name as a subdomain like
<skapp>.hns.siasky.net or a Base32-encoded subdomain.
If linking to code host on Skynet that is external from your project, you should use immutable skylinks when possible so that later updates don't risk breaking your code.
To be a proper "skapp," your application shouldn't rely on external, centralized services to function. This means external requests to APIs for on-network storage or computation that would make your skapp's data not interoperable with other skapps. Web3 apps that use wallets to interact with blockchains are a good example of relying on external, decentralized services.
Do not hardcode a specific portal domain into your code! This can be helpful for local development, but be sure to remove this before deploying to Skynet. Otherwise, the code is forced to use a portal other than the one it is being served from and works against the decentralized design of Skynet.