Giter Site home page Giter Site logo

consensys / doc.quorum-key-manager Goto Github PK

View Code? Open in Web Editor NEW
6.0 5.0 10.0 3.1 MB

Quorum Key Manager documentation

Home Page: https://docs.qkm.consensys.net/

License: Apache License 2.0

JavaScript 33.59% Shell 0.65% TypeScript 11.08% CSS 54.67%
documentation quorum key-manager doctools

doc.quorum-key-manager's Introduction

ConsenSys Quorum Key Manager

This documentation repo is built using Docusaurus 2.

Local Development

$ npm install
$ npm run prepare
$ npm start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

$ npm run build

This command generates static content into the build directory and can be served using any static contents hosting service.

doc.quorum-key-manager's People

Contributors

alexandratran avatar bgravenorst avatar dependabot[bot] avatar ezzahhh avatar ggarri avatar joshuafernandes avatar nicolasmassart avatar rolandtyler avatar toanalien avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

doc.quorum-key-manager's Issues

Migrate Quorum Key Manager doc to new Doctools

See https://github.com/ConsenSys/doc.quorum-key-manager for doc source code.

To do

  • Create a github issue for migrating this doc (on the doc repos)
  • Exact site name: no change
  • Expected domain: https://consensys.net/docs/quorum-key-manager/
  • Logo (SVG): no change
  • Colour palette: no change
  • Define content license: no change
  • integrate design elements (no change for now, migrating as is)
  • Have agreement from the Tessera team
  • Make sure all pending PRs are merged before starting
  • Disable Github repos interaction for 1 week to make sure no collisions in PRs
  • Disable Github webhooks with RTD and Circle CI
  • Disable Circle CI build (in circle project config)
  • Create a new main branch from master (next default will be main)
  • Remove everything except /docs content and mkdocs.yml file
  • Copy files from doctools.template except /docs
  • Update mkdocs.*.yml files
  • Update Docker compose file
  • Preview the site locally
  • Make adjustments (logo, favicon)
  • Update Readme
  • Create production and preview environments on Github
  • Create production secrets (see doctools.template)
  • Create the Cloudflare KV entry
  • Push the main branch to upstream: the migration has to be on a branch in the upstream repos, not a fork!
  • Create a first PR to activate workflows (add “fixes #” to close the initial issue automatically
  • Setup branch rule for main and require workflow
  • Setup @ConsenSys/consensys-docops team as admin on repo and keep @ConsenSys/protocol-pliny as maintainers
  • Test the new doc site is published on new URL consensys.net/docs/quorum-key-manager
  • Setup main as default branch
  • Create release for the latest stable version
  • Update Cloudflare DNS CNAMEs
  • Test the old doc site domain redirects to the new docs.quorum-key-manager.consensys.net
  • Restore Github interactions
  • Communicate on the new doc site

ConsenSys product contact

#team-quorum-key-manager (PM @julien-marchand )

update curve name

The BN254 curve was renamed to "Babyjubjub", which is an alias for "BN254 - twisted edwards."

Wrong Environment Variable Name for Setting TLS/SSL Mode

Describe the bug

Documentation for TLS/SSL has the wrong environment variable name DB_SSLMODE:
https://github.com/ConsenSys/doc.quorum-key-manager/blob/127f0e22e7993d0e0da3669af617aee8250a7608/docs/Reference/CLI/CLI-Syntax.md?plain=1#L289

  • Missing content
  • Outdated content
  • Wrong content
  • Confusing or misleading content
  • Other

Change suggestion

Environment variable name should be DB_TLS_SSLMODE as shown in the docker compose example here:
https://github.com/ConsenSys/quorum-key-manager/blob/d509f52d9ab3d6476327415a6d276f4e570b50e2/docker-compose.yml#L9

Add documentation for LTS (Long Term Support)

QKM now provides LTS releases.

Add a page describing the LTS releases and what they mean.

  • How long is an LTS release supported?
  • Will we be publishing interim releases between LTS releases
  • How do users know that a release is an LTS release? (e.g. is it numbered differently)
  • How often are LTS releases published?
  • What's the difference between interim releases and LTS releases

Document authorization

Document a description of authorization and authorization policies, and instructions for how to use authorization.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.