Skip to content

Commit

Permalink
Merge pull request #64 from hoprnet/main
Browse files Browse the repository at this point in the history
Additional hotfix for the Valencia release
  • Loading branch information
tropicar authored Dec 9, 2022
2 parents b83cda4 + 712c96d commit 8113bbe
Show file tree
Hide file tree
Showing 3 changed files with 24 additions and 4 deletions.
20 changes: 20 additions & 0 deletions DEVELOPING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Repository structure


There are two repositories:

- official: https://github.com/dappnode/DAppNodePackage-Hopr
- internal: https://github.com/hoprnet/DAppNodePackage-Hopr

The `internal` is a fork of the `official` one.

Tha development happens on the internal repository and it has two branches:

- `develop` which contains the edge version, not meant for publishing
- `main` which is supposed to be in-sync with the `main` branch on the `official` repo


PRs are only meant to be made from the `internal` repo's `main` branch to the `official` repo's `main` branch.



4 changes: 2 additions & 2 deletions dappnode_package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "hopr.public.dappnode.eth",
"version": "1.0.2",
"upstreamVersion": "v1.90.63",
"version": "1.0.3",
"upstreamVersion": "v1.90.68",
"description": "The HOPR protocol ensures everyone has control of their privacy, data, and identity. By running a HOPR Node, you can obtain HOPR tokens by relaying data and connect to the HOPR Network.",
"type": "service",
"architectures": ["linux/amd64"],
Expand Down
4 changes: 2 additions & 2 deletions docker-compose.yml
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
version: "3.5"
services:
node:
image: "node.hopr.public.dappnode.eth:1.0.2"
image: "node.hopr.public.dappnode.eth:1.0.3"
build:
context: .
args:
UPSTREAM_VERSION: 1.90.63
UPSTREAM_VERSION: 1.90.68
ports:
- "9091:9091/tcp"
- "9091:9091/udp"
Expand Down

0 comments on commit 8113bbe

Please sign in to comment.