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

$ epnd site publish ./out --name shop$ epnd site gramx domain-add shop.example.com --gramx <your-gramx>$ epnd site gramx route shop.example.com shop --gramx <your-gramx>$ epnd site list webtest2 https://saturn-crux-50gramx-50.gramx.50gramx.com last 7 days: 316629 requests from 5518 networks, 17812.5 MB; 14% by bots and crawlers version ab44f052b217 (8387 files, 632.1 MB; 0 earlier kept) fabric https://apogee-sagitta-50gramx-50.gramx.50gramx.com last 7 days: 72 requests from 15 networks, 1.3 MB; 12% by bots and crawlers version 743ca7401477 (2 files, 0.1 MB; 6 earlier kept)
The same build output (a static folder) you deploy today.
The edges keep serving what they have cached, and fetch anything else from another gram that holds a copy. That is why a site should have more than one holder: add a second gram to your gramx, or let your own other grams hold it.
Yes. You add one TXT record to prove the domain is yours and point it at the gramx. The gram checks for the records every minute and the edges start serving as soon as they see them.
Anything that builds to a folder of static files. 50gramx.com itself is a Next.js static export of about 11,000 files. Server-side rendering on request is not offered yet.
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.