offbyn
/
nostrweb
forked from nostr/nostrweb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
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.
88 Commits
1 Branch
0 Tags
95 KiB
JavaScript 59.5%
CSS 22.6%
HTML 17.9%
 
 
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cd99b5e5c1'
${ noResults }
Go to file
OFF0 cd99b5e5c1
feed: add deeplinking and browser history 
Added deeplinks with browser history support. Each note and author
have now a detail view under nostr.ch/<event-id-or-pubkey> in a
future commit also /e/<event-id> and /p/<pubkey> could be supported.

User can now navigate with browser back (with the expection of the
settings overlay).

Not everything is supported in the detail view (yet) i.e reply and
stars are partially working (dont update visually), leaving this as
open bug. This should fix itself once only 1 render container is
used instead of different divs in the html for each view.

Ideally the detail view should also query for related events,
something to add in a future commit
 		2 years ago
src feed: add deeplinking and browser history 2 years ago
tools add an about page 2 years ago
.gitignore initial 2 years ago
.woodpecker.yml add an about page 2 years ago
LICENSE initial 2 years ago
README.md docs: update links in the readme file 2 years ago
esbuildconf.js pwa: add manifest and related app icons 2 years ago
package-lock.json 0.0.11 2 years ago
package.json 0.0.11 2 years ago

README.md

nostr web client

this is a web interface to nostr. a live instance is hosted at https://nostr.ch/

some useful resources:

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

  1. make sure version field in package.json as seen by remote git on master branch matches the tag created in the next step.
  2. tag a commit on master branch with a git tag v<vesion>.
  3. 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.