a nostr web interface in vanilla JS https://nostr.ch/
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
OFF0 4576355b03
ci/woodpecker/pr/woodpecker Pipeline was successful Details
ci/woodpecker/push/woodpecker Pipeline was successful Details
layout: visual interface improvements
- writing a new message is now presented in full-screen, so that
  there are no distractions, i.e. other posts
- added back button and listen to esc key to close new message
- on portrait mode the navigation buttons are now positioned at
  the bottom of the screen
- write new message botton (bubble) is also positioned bottomright
- replies now use a line to the last reply instead of indentation,
  better use of available space, especially on small screen
- ignore newlines at the end of a post
- added subtile growin effect to the multiline textfield, to hint
  that the textarea is growing with more content
2 years ago
src layout: visual interface improvements 2 years ago
tools ci: rsync dist/ over to the live server 2 years ago
.gitignore initial 2 years ago
.woodpecker.yml ci: remove "branch" from conditional release pipeline execution 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 0.0.5 2 years ago
package.json 0.0.5 2 years ago

README.md

nostr web sandbox

a playground for a web interface to nostr. 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.