ETHBrno² Website
https://ethbrno.cz
1b287ba682 | ||
---|---|---|
data | ||
scripts | ||
src | ||
static | ||
tests | ||
.env.example | ||
.eslintignore | ||
.eslintrc.cjs | ||
.gitignore | ||
.nojekyll | ||
.npmrc | ||
.nvmrc | ||
.prettierignore | ||
.prettierrc | ||
.woodpecker.yml | ||
README.md | ||
package-lock.json | ||
package.json | ||
playwright.config.js | ||
postcss.config.cjs | ||
svelte.config.js | ||
tailwind.config.cjs | ||
vite.config.js |
README.md
ETHBrno² Website
Website is created using SvelteKit and deployed as a static application to these addresses:
- ethbrno.cz (self-hosted @ gwei.cz)
- mirror.ethbrno.cz (mirror @ Netlify)
- IPFS network - the url is changing (example: bafybeiddx4e2yyur3kjyppcvcg2nb7yxrxs2b2y7lfe4pgekgwpjwtsh7y.ipfs.gwei.cz)
The IPFS addresses of the major versions are stored directly in the ethbrno.eth
ENS record. You can access the site using these gateways:
Site is configured to prerender all content and refresh the data from Arweave. Publishing script is named upload-data and require your own Arweave wallet (whole JSON string) as an AR parameter in the environment, like AR={"kty":"RSA","n":....
. IPFS publishing is not prepared out of the box, but it basically takes output of /build
and send it to the ipfs pinning service like Pinata. We are using self hosted server for this.