Use ghcr via gha instead of DockerHub via TravisCI

.gitattributes

@@ -0,0 +1 @@
+*.sol linguist-language=Solidity

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+### Description
+
+<!-- Brief description of the code changes. Add supporting screenshots and videos where applicable. -->
+
+### Motivation
+
+<!-- If this PR does not close any issue, state the motivation behind the PR here. -->
+
+### Related issues and PRs
+
+<!-- Please link issues and other PR's on which this PR depends. -->
+
+### How has this been tested
+
+<!-- How others should test your changes and check for any possible regressions. -->
+
+- [ ] Step 1
+
+### Checklist
+
+<!-- Go over the checklist, and put an `x` in all the boxes when you confirm they have been done. -->
+
+- [ ] I have reviewed the code changes myself
+- [ ] My code meets all of the acceptance criteria of the issue it closes.
+- [ ] I have made all necessary changes to the documentation.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.
+- [ ] Any dependent changes have been merged and published.

.github/dependabot.yml

@@ -0,0 +1,23 @@
+version: 2
+
+updates:
+  # Enable version updates for npm
+  - package-ecosystem: "npm"
+    # Look for `package.json` and `lock` files in the `root` directory
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Enable version updates for Docker
+  - package-ecosystem: "docker"
+    # Look for a `Dockerfile` in the `root` directory
+    # Expand for subdirectories
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Enable version updates for GitHub-Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/release.yml

@@ -0,0 +1,34 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  push:
+    runs-on: ubuntu-latest
+    permissions:
+      packages: write
+      contents: read
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Setup node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: 14.x
+          registry-url: http://registry.npmjs.org/
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Log into GitHub container registry
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Build images
+        run: npm run build
+
+      - name: Push images
+        run: npm run deploy

.gitignore

@@ -2,5 +2,8 @@
 .DS_Store
 **/.DS_Store
 .idea/
-node_modules/
+.vscode/
+
 *.swp
+
+node_modules/

.husky/.gitignore

@@ -0,0 +1 @@
+_

.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx --no-install commitlint --edit "$1"

CONTRIBUTING.md

@@ -6,86 +6,57 @@ Please note we have a code of conduct, please follow it in all your interactions
 
 ## Pull Request Process
 
-1. Ensure any install or build dependencies are removed before the end of the layer when doing a
-   build.
-2. Update the README.md with details of changes to the interface, this includes new environment
-   variables, exposed ports, useful file locations and container parameters.
-3. Increase the version numbers in any examples files and the README.md to the new version that this
-   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
-4. You may merge the Pull Request in once you have the sign-off of another developer, or if you
-   do not have permission to do that, you may request the second reviewer to merge it for you.
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
+2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of another developer, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
 
 ## Code of Conduct
 
 ### Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ### Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to creating a positive environment include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ### Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ### Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
 ### Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [MaibornWolff@users.noreply.github.com]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [MaibornWolff@users.noreply.github.com].
+All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
 Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 
 ### Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
 [version]: http://contributor-covenant.org/version/1/4/

README.md

@@ -1,9 +1,9 @@
 # Ethereum Development Environment and Network (EDEN)
 
-[![Build Status](https://travis-ci.com/MaibornWolff/eden.svg?branch=master)](https://travis-ci.com/MaibornWolff/eden)
-
 **E**thereum **D**evelopment **E**nvironment and **N**etwork is a collection of tools and templates to enable app developers to create new prototypes fast and effectively.
 
+![Screenshot of the EDEN dashboard](/docs/images/dashboard.png)
+
 ## Contents
 
 - Private PoA geth blockchain including bootnode, fullnode, miners, explorers and monitors
@@ -12,15 +12,13 @@
 
 - Private PoA parity blockchain including authorities, members, explorers and monitors
 
-- Toolbox with Truffle, Oyente and some development utilities
+- Toolbox with Truffle, Oyente, Smartcheck and Mythril as analyzer as well as other development utilities
 
-- Open-Ethereum development chain including explorer, monitor and dashboard
+- Single SKALE node environment
 
 - Private IPFS network including IPFS peers and clusters
 
-- Single SKALE node environment
-
-![Screenshot of the EDEN dashboard](/doc/img/eden_grafik.png)
+- Open-Ethereum development chain including explorer, monitor and dashboard
 
 ## Getting Started
 
@@ -46,7 +44,7 @@ Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduc
 
 ## Versioning
 
-We use [SemVer](http://semver.org) for versioning. For the versions available, see the [tags on this repository](tags).
+We use [SemVer](http://semver.org) for versioning.
 
 ## Authors
 

geth-poa-docker/README.md

@@ -5,17 +5,17 @@ A set of Docker images to create a local PoA Ethereum network with one bootnode,
 The testnet consists of several parts:
 
 - 1 bootnode: registers existing nodes on the network, discovery service.
-- 2 miners: also called **sealers** within proof-of-authority (PoA). They validate the blocks.
+- 2 miners: also called **sealers** within PoA. They validate the blocks.
 - 1 fullnode: this serves as **transaction relay** and is a fullnode that does not mine, is locked but has RPC exposed.
 - 2 swarm bee nodes: these nodes make up the **peer-to-peer CDN**.
 - 3 blockchain explorer: 2 lightweight web applications to explore the blockchain and 1 blockscout explorer.
 - 1 monitor and its corresponding dashboard: the monitor collects data from the fullnode which is displayed through the dashboard.
 
 ## Quick start
 
-Setting up this network requires you to install Docker and Docker Compose. Clone the repository, and run `docker-compose up` or use Makefile commands from this directory.
+Setting up this network requires you to install Docker and Docker Compose. Clone the repository, run `docker-compose up` or use Makefile commands from this directory.
 
-```
+```bash
 # Start the network
 $ make start
 # Restart the network
@@ -36,15 +36,23 @@ The nodes in the network are connecting with the bootnode. This is a special Eth
 
 There are three nodes that participate in the network. The state is synchronized between them and they are trying to create blocks with mining. Initially, they connect to the bootnode with the information derived from the fixed IP and the `nodekeyhex`. If you want to interact with the network, you need to connect via RPC. You can attach a geth instance, connect Remix IDE or connect your browser with web3 and build a dApp.
 
-The RPC Ports of the nodes are mapped to your localhost, the addresses are:
+The RPC ports of the nodes are mapped to your localhost, the addresses are:
 
 - geth-dev-miner-1: [http://localhost:8541](http://localhost:8541)
 - geth-dev-miner-2: [http://localhost:8543](http://localhost:8543)
 - geth-dev-node: [http://localhost:8545](http://localhost:8545)
 
-### Swarm bee / IPFS
+### Swarm bee
+
+Swarm is a decentralised data storage and content distribution technology, in other words, it is the "decentralized storage piece in dApps".
+The primary objective of Swarm is to provide a sufficiently decentralized and redundant store of Ethereum’s public record, in particular to store and distribute dapp code and data as well as blockchain data.
+Swarm Bee is the successor of the Ethereum Swarm client aiming for a production-ready version of Swarm.
+Note that Bee does not currently expose every feature of the original Swarm client
+
+The ports of the nodes are mapped to your localhost, the addresses are:
 
-Work in progress
+- bee-1: [http://localhost:1633](http://localhost:1633)
+- bee-2: [http://localhost:2633](http://localhost:2633)
 
 ### Blockchain explorer
 

geth-poa-docker/blockscout/Dockerfile

@@ -1,5 +1,7 @@
 FROM bitwalker/alpine-elixir-phoenix:1.11.3
 
+LABEL org.opencontainers.image.source https://github.com/maibornwolff/eden
+
 RUN apk --no-cache --update add alpine-sdk gmp-dev automake libtool inotify-tools autoconf python3 git
 
 # Get Rust

geth-poa-docker/bootnode/Dockerfile

@@ -1,5 +1,7 @@
 FROM ubuntu:xenial
 
+LABEL org.opencontainers.image.source https://github.com/maibornwolff/eden
+
 RUN apt-get update \
     && apt-get install -y wget software-properties-common \
     && rm -rf /var/lib/apt/lists/*