Deployment Scripts contains scripts used to run blockchain services at Blockchain Commons.
/etc/nagios4: Configuration for nagios4 monitoring.- Nagios configuration reference can be found here: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/toc.html.
Also see our standard Bitcoin setup with Bitcoin Standup Scripts.
NB: Do not commit any credentials to this repository. Any credentials/keys should be configured as $USER variables in etc\nagios4\resource.cfg. We use the following:
$USER2: Tor proxy port.$USER3: Username for BlockckainCommons Bitcoin RPC.$USER4: RPC auth password generated using https://github.com/bitcoin/bitcoin/blob/master/share/rpcauth/rpcauth.py.
- Define hosts to be monitored in: etc\nagios4\servers\servers.cfg
- List contact details in etc\nagios4\objects\contacts.cfg.
- There are several alternative setups for email notifications:
- Using Gmail
- Using external SMTP
- Run a Linode mail-server on a subdomain
- Modify any
notify-host-by-emailcommanddirectives inetc/nagios4/commands.cfgto use the settings you have configured for sending email.
- The hostname for a Tor hidden service is read using:
cat /var/lib/tor/$HOSTNAME/hostname - Modify any
service.check_commanddirectives to use thecheck_http! -p $USER2to monitor hidden services.$USER2is a variable configured in etc\nagios4\resource.cfg.
deployment-scripts is used for installing and maintaining BlockchainCommons infrastructure and so it's under continuous development.
To use deployment-scripts you'll need to use the following tools:
- A Debian Linode VPS.
- Nagios4.
- Tor
deployment-scripts is a project of Blockchain Commons. We are proudly a "not-for-profit" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.
To financially support further development of deployment-scripts and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a GitHub Sponsor. You can also support Blockchain Commons with bitcoins at our BTCPay Server.
We encourage public contributions through issues and pull requests! Please review CONTRIBUTING.md for details on our development process. All contributions to this repository require a GPG signed Contributor License Agreement.
The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.
Gordian Developer Community. For standards and open-source developers who want to talk about interoperable wallet specifications, please use the Discussions area of the Gordian Developer Community repo. This is where you talk about Gordian specifications such as Gordian Envelope, bc-shamir, Sharded Secret Key Reconstruction, and bc-ur as well as the larger Gordian Architecture, its Principles of independence, privacy, resilience, and openness, and its macro-architectural ideas such as functional partition (including airgapping, the original name of this community).
Gordian User Community. For users of the Gordian reference apps, including Gordian Coordinator, Gordian Seed Tool, Gordian Server, Gordian Wallet, and SpotBit as well as our whole series of CLI apps. This is a place to talk about bug reports and feature requests as well as to explore how our reference apps embody the Gordian Principles.
Blockchain Commons Discussions. For developers, interns, and patrons of Blockchain Commons, please use the discussions area of the Community repo to talk about general Blockchain Commons issues, the intern program, or topics other than those covered by the Gordian Developer Community or the Gordian User Community.
As an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. Please consider the discussions area as a locale where you might get answers to questions. Alternatively, please use this repository's issues feature. Unfortunately, we can not make any promises on response time.
If your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.
The following people directly contributed to this repository. You can add your name here by getting involved. The first step is learning how to contribute from our CONTRIBUTING.md documentation.
| Name | Role | Github | GPG Fingerprint | |
|---|---|---|---|---|
| Christopher Allen | Principal Architect | @ChristopherA | <[email protected]> | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
| Nicholas Ochiel | Site Reliability Engineering | @nochiel | <[email protected]> | 45EA 5C81 9B7E E915 C2A2 7C64 4444 1190 7BE8 83D9 |
We want to keep all of our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.
We do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.
Please report suspected security vulnerabilities in private via email to [email protected] (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.
The following keys may be used to communicate sensitive information to developers:
| Name | Fingerprint |
|---|---|
| Christopher Allen | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
You can import a key by running the following command with that individual’s fingerprint: gpg --recv-keys "<fingerprint>" Ensure that you put quotes around fingerprints that contain spaces.