50GRAMx Sites

From Firebase Hosting to Sites.

Publishes a website from a folder or a build, and serves it from your own grams with the network’s edges in front.

Firebase HostingSites

The steps

  1. 1
    Build as you do nowKeep your framework and build command; the output folder is what gets published.
  2. 2
    Point the gramx at the sourceA gramx site follows its source (a .tar.gz and its SHA-256); any member gram with the deployer rank publishes each new build.
  3. 3
    Move the domainNames sets the records; the old host can stay until the new one answers.
  4. 4
    Keep old addressesEvery address the site ever published redirects to its nearest page, so links and search results keep working.

What changes

  • The site lives on machines you own; edges only carry it to strangers.
  • Hosting belongs to the gramx (the business), not to one person’s account.
  • Firebase Hosting bills on storage, data transferred. Here the work is metered on compute, storage and data served, and on your own grams it is credited back.

What stays the same

The same build output (a static folder) you deploy today.

Start with Evo

Evo works on your own gram, with your machines in view, and asks before every change. Take one of these to it, or write your own.

  1. 1. Run a gramOn a machine you have. Evo lives there.
  2. 2. Enter your gramxYour business on the network.
  3. 3. Ask EvoPaste the question; it works through it with you.