Skip to content
This repository was archived by the owner on Sep 15, 2020. It is now read-only.

Dockerfile Design by Use Case

Jump to bottom
jayDayZee edited this page May 29, 2017 · 1 revision

use cases

  1. core developer
  2. app developer
  3. multi-node testing (same as app developer as far as I can tell)
  4. end-user / package manager

details

  1. core developer
  • build and test current source code
  • potentially run debugger inside container, accessible from the outside world
    • Ive made this work. It does... required go to be installed on the host system, so.. lol
  1. app developer
  • build a test current source code
  • integration / multi-node testing
  • deploy?
  1. multi-node testing
  • this has been referred to as "headless" (I believe), but I cant see any functional differences between the requirements for this, and for any other dockerfiles
  1. end-user / package manager
  • core is a docker image
  • app is a docker image which is mounted into the code
    • since the app is not compiled code, the docker image is simply a docker image of the filesystem
    • since the image hash is a hash of the content, this is sufficient for security purposes
Project Links: Holochain Overview Code Repository White Paper GoDocs API Reference

Holochain is part of Ceptr, and brought to you by the MetaCurrency Project

Please see our new documentation site at developer.holochain.org.

Intro

External Links

Holochain Core Development

Dev pages, need integrating into the wiki

Docker install for Devs

Clone this wiki locally
⌂ 换网址