4EVERLAND Documents
HomeTwitterDiscordBlogs
  • Welcome to 4EVERLAND
  • Get started
    • Our Features
    • Quick Start Guide
      • Registration
      • Login options
        • MetaMask
        • OKX Wallet
        • Binance Web3 Wallet
        • Bitget Wallet
        • Phantom
        • Petra
        • Lilico
      • Usage Introduction
      • Dashboard stats
      • Account
        • Linking Your EVM Wallet to 4EVERLAND Account
        • Balance Alert
    • Billing and Pricing
      • What is LAND?
      • How to Obtain LAND?
      • Pricing Model
      • Q&As
    • Tokenomics
  • HOSITNG
    • What is Hosting?
      • IPFS Hosting
      • Arweave Hosting
        • Auto-Generation of Manifest
      • Internet Computer Hosting
      • Greenfield Hosting
    • Guides
      • Creating a Deployment
        • With Git
        • With IPFS Hash
        • With a Template
      • Site Deployment
      • Domain Management
        • DNS Setup Guide
        • ENS Setup Guide
        • SNS Setup Guide
          • The gateway: 4sol.xyz
        • SPACE ID Setup Guide
      • Project Setting
        • Git
      • Troubleshooting
      • Common Frameworks
    • Hosting Templates Centre
      • Templates Configuration File
    • Quick Addition
      • Implement Github 4EVER Pin
      • Github Deployment Button
    • Hosting API
      • Create Project API
      • Deploy Project API
      • Get Task Info API
      • IPNS Deployment Update API
    • Hosting CLI
  • Storage
    • Bucket
      • IPFS Bucket
        • Get Root CID - Snapshots
      • Arweave Bucket
        • Path Manifests
          • Instructions for Building Manifest
          • Auto-Generation of Manifest
        • Arweave Tags
        • Unleash Arweave
      • Guides
      • Bucket API - S3 Compatible
        • Coding Examples
          • AWS SDK - Go (Golang)
          • AWS SDK - Java
          • AWS SDK - JavaScript
          • AWS SDK - .NET
          • AWS SDK - PHP
          • AWS SDK - Python
          • AWS SDK - Ruby
        • S3 Tags Instructions
      • 4EVER Security Token Service API
      • Bucket Tools
      • Bucket Gateway Optimizer
    • 4EVER Pin
      • Guides
      • Pinning Services API
      • IPFS Migrator
    • Storage SDK
  • Gateways
    • IPFS Gateway
    • IC Gateway
    • Arweave Gateway
    • Dedicated Gateways
      • Gateway Access Controls
      • Video Streaming
      • IPFS Image Optimizer
    • IPNS Manager
      • IPNS Manager API
  • RPC
    • Guides
    • API Keys
    • JSON Web Token (JWT)
    • What's CUs/CUPS
    • WebSockets
    • Archive Node
    • Debug API
    • Chains RPC
      • BSC / opBNB
      • Ethereum
      • Optimism
      • Polygon
      • Taiko
  • AI
    • AI RPC
      • Quick Start
      • Models
      • API Keys
      • Requests & Responses
      • Parameters
    • 4EVER Chat
  • RaaS - Beta
    • What's Rollups?
    • 4EVER Rollup Stack
  • DePIN
    • 4EVER Network
    • Storage Nodes
  • More
    • Use Cases
      • Livepeer
      • Lens Protocol
      • Optopia.ai
      • Linear Finance
      • Snapshot
      • Tape
      • Taiko
      • Hey.xyz
      • SyncSwap
    • Community
    • Tutorials
    • Security
    • 4EVERLAND FAQ
Powered by GitBook
On this page
  • Edit Configuration
  • Deploy Overview
  • Visit your deployment
  • Deleting a deployment
  1. HOSITNG
  2. Guides

Site Deployment

Last updated 10 months ago

4EVERLAND Hosting deploys every new website atomically, ensuring that there are never any discrepancies when submitting new files or making modifications to existing ones.

Once you have , you should follow the tutorial below to complete the construction.

Edit Configuration

Hosting Platform

4EVERLAND Hosting supports IPFS, Arweave, BNB Greenfield, and Internet Computer automatic deployment, please choose the platform you need to deploy according to your needs, here we take IPFS as an example.

Basic & Build Configuration

4EVERLAND Hosting will attempt to automatically detect the site's framework and apply the correct build parameters. However, in some cases you may need to enter the parameters manually during the initial site deployment phase or in the site setup after the site has been deployed.

Here are some build parameters you can modify.

  • Framework Preset: Select the framework of your choice. This selection will be used for all deployments within your Project. However, if no framework is detected, "Other" will be selected.

  • Build Command: The commands to execute to build the site. Eg: npm install && npm run build. If your frondend does not require a build, leave this field empty.

  • Output Directory: The directory in which your compiled frontend will be located. If you want to serve everything instead of a sub directory, leave this field empty.

  • Environment variables: The values of your environment variables. Eg: Game_2048.

Deploy Overview

You can find a deploy overview on the detail page of any successful deploy, right above the Building log. It allows you to quickly identify your deploy status and refer to the details in the log based on different types of information.

Sync to IPFS

Contains the Hash of the page on the IPFS.

Assigning Domains

4EVERLAND Hosting will assign two free domains to each deployment, they are name.4everland.app & name-4everlandorg.4everland.app.

Visit your deployment

You can access directly through the domains assigned by 4EVERLAND Hosting or through the way IPFS Gateway + CID.

Here we recommend using the 4EVERLAND Public IPFS Gateway for the best experience:

The 4EVERLAND public IPFS gateway is:

https://ipfs.4everland.io/ipfs/<CID>

Deleting a deployment

Deleting a Site

Deleting a site is an irreversible action so proceed with caution.

There are lots of ways to delete your project in 4EVERLAND. Click the Delete button:

Or go to the settings and navigate to Advanced > Delete Project. A modal will then appear with a warning and instructions to remove the site.

For more information about 4EVERLAND gateways please check .

If you have any questions, please join our , or send us an email at .

GATEWAYS
Discord server
contact@4everland.org
chosen a deployment method