To get started deploying a site on Skynet, create a folder with an
Uploading a site to Skynet using the siasky.net uploader
"homepage": "."to your
package.jsonbefore you build, then just upload your build folder!
Official Documentation and SDKs
SDKs marked with * above are partial implements – only
skynet-jsimplements the registry, SkyDB, MySky, and resolver skylinks. It is our recommended SDK for the time being.
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:
- 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.