commerceblock / guardnode

Covalence Guardnode daemon implementation
MIT License
1 stars 0 forks source link

docker compose #4

Open nkostoulas opened 5 years ago

nkostoulas commented 5 years ago

Build Dockerfile image for guardnode repo, similar to federation, and add to buidlkite and docker hub.

Build sample docker compose file that will later be modified on a per client basis. This consists of two images; an ocean one and a guardnode one. Both containers should have persistent access to the ocean node datadir. It should be possible to spin only the ocean container or both ocean and guardnode.

The config for the guardnode container is on README and is passed to the daemon in a similar way to federation.

Maybe have the compose files under a contrib directory with instructions.

nkostoulas commented 5 years ago

@stakauskas @mit15 I've added the requirements for this. I'll gather changes required in order to relaunch the Ocean testnet to test request creation and guardnodes. On relaunch we can add a public compose file in contrib.

mit15 commented 5 years ago

I've made a pull request with a draft template https://github.com/commerceblock/guardnode/pull/5 Let me know what you think.

stakauskas commented 5 years ago

@mit15 - we need a templating mechanism for this. Use Jinja2 with Ansible or Python scripts to generate compose files per client and separate Dockerfile for calling it.

nkostoulas commented 5 years ago

That would be fine for the guardnode part as it will be the same for all. The ocean config might differ though, would this be a problem?

stakauskas commented 5 years ago

That's fine, will need to make two sections: one for guardnode and other for ocean and depending on the client generate ocean config just with required parts.