a nostr web interface sandbox

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

alex 64170846d3 v0.0.3: bump from 0.0.2 to trigger an automated deployment i broke the ci while moving the repo from x1ddos/nostrweb to nostr/nostrweb - all settings remained in the old repo and pipelines didn't run at the new location. could've overwritten the git tag but what happens in public git, stays in git. so, just making a new dummy tag to trigger the ci.		2 years ago
src	getting ready	2 years ago
tools	ci: rsync dist/ over to the live server	2 years ago
.gitignore	initial	2 years ago
.woodpecker.yml	ci: rsync dist/ over to the live server	2 years ago
LICENSE	initial	2 years ago
README.md	docs: clarify how the live instance is currently updated from the CI	2 years ago
esbuildconf.js	getting ready	2 years ago
package-lock.json	v0.0.3: bump from 0.0.2 to trigger an automated deployment	2 years ago
package.json	v0.0.3: bump from 0.0.2 to trigger an automated deployment	2 years ago

README.md

nostr web sandbox

a playground for a web interface to nostr. some useful resources:

JS library used in this project: https://github.com/fiatjaf/nostr-tools
NIPs: https://github.com/nostr-protocol/nips
relays registry: https://nostr-registry.netlify.app/
event inspector: https://nostr.com/
a working web interface in vue.js: https://astral.ninja/
https://github.com/aljazceru/awesome-nostr

dev

nodejs v18.x and npm v8.x are recommended.

after npm install, start by running a dev server with:

npm run serve

and point a browser to http://127.0.0.1:8001/

the serve command injects a live reload snippet. to build a "production" copy, execute

npm run build

the build is done using esbuild, with a config in esbuildconf.js. the result is placed in dist directory.

release

make sure version field in package.json as seen by remote git on master branch matches the tag created in the next step.
tag a commit on master branch with a git tag v<vesion>.
push the tag to the remote: git push --tags.

the CI then receives a git tag event, executes npm run build, creates a tar.gz with all the files found in dist directory and uploads it as a new release artifact. the release is named after the tag name.

the idea is that nostr web instances are then notified about a new release, download the tar.gz archive and update their local copies. this is not yet implemented. at the moment, the CI symply rsync's dist/ with a remote on https://nostr.ch.