Skip to content
/ Taggr Public
forked from TaggrNetwork/Taggr

Decentralized social network and publishing platform.

License

Notifications You must be signed in to change notification settings

Spizzerp/Taggr

Repository files navigation

Taggr

Release proposal verification

Assume you want to verify a new release proposal with code commit <COMMIT> and binary hash <HASH>.

  1. Install Docker (only once).
  2. git clone https://github.com/TaggrNetwork/taggr.git (only once)
  3. cd taggr
  4. git fetch --all && git checkout <COMMIT>
  5. make release
  6. Verify that the printed hash matches the <HASH> value from the release page.

Release proposal

To propose a release, follow the steps above first. If they were successful, you'll find a binary release.wasm.gz in the taggr root directory. Use the printed code commit and the binary to submit a new release proposal.

Heap Backup (for stalwarts only)

  1. Open the browser JS console and trigger this command: api.call("heap_to_stable").
  2. Fetch the backup: DIR=/path/to/backup; ./backup.sh $DIR.
  3. Restore to the local replica: DIR=/path/to/backup; ./backup.sh $DIR restore.

Contributing

Refer to the local development docs for instructions on how to work with Taggr locally.

About

Decentralized social network and publishing platform.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 81.5%
  • Rust 13.5%
  • CSS 2.6%
  • JavaScript 0.7%
  • HTML 0.7%
  • Shell 0.5%
  • Other 0.5%