Merge pull request #27 from orbitdb/cleanups

Remove obsolete files and fixtures

docker/Dockerfile

@@ -1,16 +0,0 @@
-FROM node:10
-
-ENV NPM_CONFIG_PREFIX=/home/node/.npm-global
-
-WORKDIR /home/node
-
-COPY package.json ./
-COPY examples/ ./examples
-COPY src/ ./src
-COPY conf/ ./conf
-
-RUN chown -R node:node package.json examples src conf
-USER node
-
-RUN npm install babel-cli webpack \
- && npm install

docker/README.md

@@ -1,35 +0,0 @@
-# Running OrbitDB code in containers
-
-[Docker](https://github.com/docker/docker-ce) is a tool for running software in containers ie. OS-level virtualization. This directory contains the needed configuration files to:
-
-- Build base Docker images for OrbitDB
-
-
-## Base Docker image
-
-[Dockerfile](Dockerfile) defines OrbitDB base images that are based on [official node.js -image](https://hub.docker.com/_/node/). 
-
-Build local images with command (in repository root):
-
-```bash
-docker build -t orbit-db -f docker/Dockerfile .
-```
-
-After building local image, run node.js-examples inside container:
-
-```bash
-docker run -ti --rm orbit-db npm run examples:node
-```
-
-## Why would you want to run OrbitDB in container?
-
-Containers are nice because as software execution environments they are:
-- Reproducible, which helps testing and development because you can revert the container to original state by destroying it and creating it again,
-- Isolated, which guarantees that external factors like npm versions, the operating system version, or other installed software like native compilers do not affect the execution.
-
-They also make implementing virtualized networks for testing and benchmarking easier, which may help projects that use OrbitDB.
-
-## Tested versions
-
-- Docker 1.13.1 (Linux 4.17.5-100.fc27.x86_64)
-- Docker 18.06.1-ce (Linux 4.17.5-100.fc27.x86_64)

test/identities/fixtures/keys/0260baeaffa1de1e4135e5b395e0380563a622b9599d1b8e012a0f7603f516bdaa.json

@@ -1 +0,0 @@
-{"publicKey":"030d78ff62afb656ac62db1aae3b1536a614991e28bb4d721498898b7d41943396","privateKey":"6657f74ad8223ed8a169b12d4afbf1d368175e3f08b295d511131ee93c6cceeb"}

test/identities/fixtures/keys/CURRENT

@@ -1 +0,0 @@
-MANIFEST-000053

test/identities/fixtures/keys/LOG

@@ -1,5 +0,0 @@
-2023/02/16-14:47:21.828619 170a2b000 Recovering log #52
-2023/02/16-14:47:21.828667 170a2b000 Level-0 table #54: started
-2023/02/16-14:47:21.828864 170a2b000 Level-0 table #54: 1279 bytes OK
-2023/02/16-14:47:21.829422 170a2b000 Delete type=0 #52
-2023/02/16-14:47:21.829490 170a2b000 Delete type=3 #50

test/identities/fixtures/keys/LOG.old

@@ -1,5 +0,0 @@
-2023/02/16-14:46:59.958708 16e843000 Recovering log #49
-2023/02/16-14:46:59.958747 16e843000 Level-0 table #51: started
-2023/02/16-14:46:59.958926 16e843000 Level-0 table #51: 1279 bytes OK
-2023/02/16-14:46:59.959275 16e843000 Delete type=3 #47
-2023/02/16-14:46:59.959309 16e843000 Delete type=0 #49

test/identities/fixtures/keys/QmPhnEjVkYE1Ym7F5MkRUfkD6NtuSptE7ugu1Ggr149W2X.json

@@ -1 +0,0 @@
-{"publicKey":"0260baeaffa1de1e4135e5b395e0380563a622b9599d1b8e012a0f7603f516bdaa","privateKey":"198594a8de39fd97017d11996d619b3746211605a9d290964badf58bc79bdb33"}

test/identities/fixtures/keys/existing.json

@@ -1 +0,0 @@
-{"publicKey":"045756c20f03ec494d07e8dd8456f67d6bd97ca175e6c4882435fe364392f131406db3a37eebe1d634b105a57b55e4f17247c1ec8ffe04d6a95d1e0ee8bed7cfbd","privateKey":"3928a45bc5642ddef4938d30b899563e7e142b1947c3bd02c313621e311dd07e"}