Spheron is an all-in-one decentralized platform created to make the deployment of web apps easier by providing solutions that are transparent, immutable, and cryptographically verifiable.💻
Spheron’s interface is designed to provide the best experience for developers building in Web3 and or migrating from web2 to web3. Spheron helps devs to save 80% of their efforts to ship their apps in the decentralized ecosystem. And yes, Creating automation in Spheron will take less than 5 mins.
This blog aims to provide beginners with information on how to host their apps on the decentralized web using the Spheron platform.
Before we begin, It is evident that Spheron has enabled gated access to its platform and only the whitelisted users will be able to access the tools and deploy using Spheron.
Why gated access?
Since it is obvious that NFT is a key element in fostering user acceptability throughout the Web 3.0 ecosystem, Spheron offers NFT gated access for users before they begin using the platform.
Get yourself whitelisted.
Fill out this NFT Whitelisting for Spheron Beta program form to add yourself to the whitelist so that you may use the Spheron platform. Share this form to help Spheron reach out to web2 developers. Spheron promises to help users make the transition from web2 to web3 seamlessly.
Let’s get started!
How to configure the deployment?
Login to Spheron & Deploy your frontend on Decentralised Network with just a few clicks.
You can use the Spheron Protocol to connect a GitHub, Gitlab, or Bitbucket repository to a site for continuous deployment.
Connecting your website’s GitHub repository to deploy directly from there and enabling continuous deployment is the simplest method to get started.
- Pick a repository
Step 1: The user has the option to connect with their favourite provider.
Step2: Pick the repository you want to deploy.
If a user is unable to find the Repository he/she can fork it from the Git providers by configuring it from Spheron. If the user has not given access to Spheron previously, he/she will be redirected to the give access page. Confirm the access and proceed.
2. Pick your protocol
We support multiple decentralized protocols in which you can deploy your app. Pick the protocol which is most suited for your needs. Currently, we support Arweave, Skynet, Filecoin, and Pinata protocols. We are constantly working on adding multiple protocols, which will be added soon.
3. Configure your build settings
Spheron automatically suggests the default configuration for a selected framework for your ease. The user can also get control of the build settings for their site based on the framework of your app.
Configuring the deployment
Spheron lets you get more control of how you build and deploy your repository
- Owner: The organization’s name, is considered the owner of the deployment. Ex: Your Org’s name.
- Branch to Deploy: The branch of the repository to be deployed in Spheron. Ex: main, dev, etc.
- Root directory: In some projects, the top-level directory of the repository may not be the root directory of the app you’d like to build. For example, your repository might be a monorepo that has a frontend directory, which contains a stand-alone Next.js app.
In cases like this, you can specify the project root directory. If you do so, please note the following:
If you specify a root directory, then your app won’t be able to access files outside of that directory. You also cannot use it to move up a level.
Spheron has an auto-detect framework option, making it seamless for you by applying appropriate build parameters according to your selected repository. The parameters can also be manually entered, either during the initial site deployment stage or later in the project settings after the project has been deployed.
Below are the build parameters which you can modify.
- Package Manager: It helps create project environments and easily import external dependencies. You can choose your package manager here. Ex: npm && yarn
- Build command: The commands to execute to build the site. Ex: npm install && npm run build
- Publish directory: The name of the directory containing the file of your site after it has been built
Advanced Build Settings
Build Environment Variables are currently included in Advanced Build Settings. During the construction, you can access Project’s environment variables. This allows you to adjust behavior based on deploy settings or include information in your repository that you don’t want to save, such as API keys.
You can access the environment variables by following these 2 steps:
- In Create a new site > Step 3: Build Options, and deploy! > Advanced Build Settings
- In Project settings > Environment variables.
NOTE: Adding Environment Variables during new deployment won’t work if the project already exists, you have to add environment variables by going to your Project Settings -> Environment Variables
DEPLOY TO APPLY CHANGE: Environment variable changes are applied at deploy time and require a re-deploy to take effect.
Upon successful selection of all the parameters, click the Deploy button to deploy your app.
Your deployment will start and the deployment logs will be visible on the screen.
With these simple streamlined steps, a user can deploy their DApps into the decentralized web and #DeCloudYourself
What makes Spheron Unique?
Spheron makes front-end web deployment easy, effective, and efficient through its blockchain-based platform that takes your web app to the DSNs (Decentralised Storage Networks). Spheron removes the hurdles of centralization and censorship through blockchain, ensuring that your web app is permanently deployed and experiences 99.99% uptime throughout its life.