Tin Toy - A tiny Steem testnet based on tinman by Steemit, Inc.
docker run -d -P inertia/tintoy:latestAs Seen from Kitematic
If you want to modify the scripts before deploying:
git clone https://gist.github.com/b88e7bfff8862858e54c59392e2bce20.git tintoy
cd tintoy
docker build -t myname/tintoy:mybranch .
docker run -d -P myname/tintoy:mybranchFor example, you can modify the first line of Dockerfile to switch versions of steemd.
Tin Toy uses:
FROM steemit/steem:masterBut you can switch to any branch and try it out. Suggested branches to try can be found in steem/branches/active.
Say we want to take a look at a branch like 3103-delegation-pools. Change the first line of the Dockerfile to:
FROM steemit/steem:3103-delegation-poolsThen build and run. At the time of writing, issue #3103 added basic functionality of delegation pools, but was not yet merged to master, so this is a great way to get an early peek of branches still in development.
- Use
docker psto get the name of the existing container. - Use the command
docker exec -it <container name> /bin/bashto get a bash shell in the container.
Once the docker container has fully deployed, you'll have access to various port. Internally, the docker container responds to:
| Port | Purpose |
|---|---|
| 2001 | p2p |
| 8080 | condenser |
| 8091 | json-rpc |
| 5000 | tinman server (if enabled) |
If you launched with -P (ephemeral ports enabled), you can get a list of ports:
docker psWhich might return something like:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
290810dba18e inertia/tintoy:latest "/bin/sh -c /app/boo…" 5 minutes ago Up 5 minutes 0.0.0.0:32832->2001/tcp, 0.0.0.0:32831->8080/tcp, 0.0.0.0:32830->8090/tcp, 0.0.0.0:32829->8091/tcp tintoy
From the port list we can determine the external port for condenser. For port 8080, this example uses port 32831. Therefore, the URL to access condenser is:
http://localhost:32831
Remember, this changes whenever you execute with -P.
Occasionally, it's a good idea to refresh the sample-snapshot.json file. This process is usually only required to be performed by the repo maintainer, but if you want to do it yourself, here are the steps:
- Install
tinmanby following that product's README.md. - Next, generate a new snapshot.
- Example:
tinman snapshot -s https://anyx.io -o - | pv > snapshot.json
- Once we have our new snapshot, create a sample, overwriting the previous one.
- FIXME Example:
tinman sample -i snapshot.json -o sample-snapshot.json
- Delete (or move)
snapshot.json(we don't need it anymore now that we havesample-snapshot.json).
