https://github.com/dedis/columbus-cli
Naive implementation of a Blockchain explorer
https://github.com/dedis/columbus-cli
blockchain-explorer blockchain-visualizer typescript
Last synced: 9 months ago
JSON representation
Naive implementation of a Blockchain explorer
- Host: GitHub
- URL: https://github.com/dedis/columbus-cli
- Owner: dedis
- License: agpl-3.0
- Created: 2020-02-14T14:36:55.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2023-01-06T02:32:50.000Z (over 3 years ago)
- Last Synced: 2023-03-11T19:18:09.241Z (over 3 years ago)
- Topics: blockchain-explorer, blockchain-visualizer, typescript
- Language: TypeScript
- Homepage: https://wookiee.ch/columbus-cli/
- Size: 9.67 MB
- Stars: 3
- Watchers: 5
- Forks: 2
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# columbus-cli
Naive implementation of a Blockchain visualizer that works with cothority >= 3.4.3.
Run with `npm install && npm run bundle`
[Play with it](https://wookiee.ch/columbus-cli/)
## About Continuous Deployment (CD)
Each update on the `production` branch triggers a deployment on the production
server. Therefore, the produciton branch must only be used to make a new
deployment by updating it from the master branch with:
```bash
# Trigger a deployment:
git push origin master:production
```
Here is the simple setup we followed for continuous deployment:
**1**:
Create and set-up an ssh key so that Github can authenticate to the production
server:
```bash
ssh-keygen -t rsa -b 4096 -C "columbus-cli-rsync-github"
```
Add the private key as a secret from the repository setting with the DEPLOY_KEY
name (*Repository* > Settings > Secrets > New secret).
**2**:
Write the action that triggers an `rsync` upon changes on the production branch.
See `.github/workflows/deploy.yml`.
**3**:
Authorize the key on the server side to only execute rsync. Add in the
`~/.ssh/authorized_keys`:
```bash
command="rsync --server -vlogDtprc --delete . /var/www/wookiee.ch/public_html/columbus" ssh-rsa PUBLIC_SSH_KEY
```
**4**:
To make a deployment on the production server, update the production branch from
master with `git push origin master:production`.
This process is semi-automatic, as we know it's hard to maintain a 100% safe
master branch and it gives us more control on the deployment.