You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
execute the build process to generate a docker image for the specified role
the Dockerfile will download and call setup_federated_node.py itself, to build the federated node in the docker image with the approprite command line options
(we will use this all with automated builds on dockerhub, and each build variant will be a tag)
Images I'd be planning:
counterwallet_bitcoind: Uses bitcoind, no insight (uses blockr.io), and auto downloads the bitcoind blockchain data and counterpartyd and counterblock databases on first boot via bittorrent or s3 site
counterwallet_simple: Uses pyrpcwallet (and blockr.io), no insight (uses blockr.io), and auto downloads the counterpartyd and counterblock databases on first boot via bittorrent or s3 site
counterpartyd_simple: Same as counterwallet_simple, but only runs counterpartyd, with open port access and rpc/1234 username/password on rpc services by default...allows easy dev counterpartyd access
Future possible images:
counterwallet_full: Uses bitcoind and insight. Blockchain data must manually download
vending_machine
autobtcescrow_agent
whatever else
More notes:
build logic for everything except ubuntu 14.04 can then be ripped out (I'm thinking) of setup_federated_node.py since other OSes can just use the docker image. alert users to this because this is disruptive though
ubuntu 14.04-based systems can still use setup_federated_node.py directly. this is especially important for production servers where we want everything to run on bare metal, and the hardware is dedicated (e.g. counterwallet.co)
also, include plenty of documentation for using the docker images on windows, macos, and other versions of linux
create Dockerfiles and build_docker.py script that will:
(we will use this all with automated builds on dockerhub, and each build variant will be a tag)
Images I'd be planning:
Future possible images:
More notes:
Docker resources:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: