contains-io/containment

Issues

• The default package list is not appropropriate for actual install

  #71 opened 6 years ago by zancas
  0

• There's not an editable Dockerfile that contains the most up-to-date state of the containment, in the project.

  #70 opened 6 years ago by zancas
  0

• If the external User has an ssh-agent it should be available inside the containment

  #67 opened 6 years ago by zancas
  0

• The new "objectified" architecture no longer requires "build.py"

  #64 opened 6 years ago by zancas
  0

• For the POC we will use ubuntu:latest

  #65 opened 6 years ago by zancas
  0

• Architecture notes

  #52 opened 8 years ago by zancas
  0

• register package to PyPI

  #53 opened 8 years ago by zancas
  0

• Need to implement preferences parser.

  #55 opened 8 years ago by zancas
  8

• There is no parser for the preferences.ini file

  #56 opened 8 years ago by zancas
  0

• There are no docs for preferences

  #58 opened 8 years ago by zancas
  0

• The preferences parser is untested.

  #57 opened 8 years ago by zancas
  0

• containenv is a deprecated name, we're now called "contain"

  #59 opened 8 years ago by zancas
  1

• A nice (possibly) necessary abstraction is to make the "PROJECT" a Python class.

  #31 opened 8 years ago by zancas
  1

• Using __doc__ as the description field of "tasks" may cause i18n issues.

  #29 opened 8 years ago by zancas
  1

• Subcommands should be arguments to the primary command.

  #15 opened 8 years ago by dangle
  2

• Use six to automatically support 2/3 compatibility.

  #13 opened 8 years ago by zancas
  1

• register domain name for containenv

  #54 opened 8 years ago by zancas
  2

• convert `runcontainenv.sh` to `runcontainenv.py`

  #50 opened 8 years ago by zancas
  0

• Add access to host docker daemon to all containenv (by default)

  #47 opened 8 years ago by zancas
  0

• Make `metasource` the WORKDIR of the containenv.

  #48 opened 8 years ago by zancas
  0

• Refactor atop `rapcom >= 0.1.1`

  #42 opened 8 years ago by zancas
  1

• make docopt 'command' into an arg

  #24 opened 8 years ago by zancas
  1

• Autodetect architecture for FROM images.

  #45 opened 8 years ago by dangle
  0

• Define `~/.containenv/containenvrc` format

  #38 opened 8 years ago by zancas
  3

• Implement `~/.containenv/Dockerfile.PROJECT` write operation

  #41 opened 8 years ago by zancas
  0

• Implement image publish

  #40 opened 8 years ago by zancas
  0

• Write default `.containenvrc`, and add to package_data

  #39 opened 8 years ago by zancas
  0

• Consume `~/.containenvrc`

  #37 opened 8 years ago by zancas
  0

• containenv init can be decomposed into a sequence of tasks, we'll work them out here.

  #11 opened 8 years ago by zancas
  1

• containenv should be language-agnostic

  #7 opened 8 years ago by jputrino
  3

• setup.py needs console script for "contain"

  #4 opened 8 years ago by szakeri
  0

• Implement most basic flow: containenv && containenv activate

  #2 opened 8 years ago by zancas
  3

• implement `containenv init` tasks

  #25 opened 8 years ago by zancas
  4

• containenv should support development from start to finish

  #34 opened 8 years ago by dangle
  0

• Containenv currently only supports git, we certainly want to support hg and more ASAP.

  #33 opened 8 years ago by zancas
  0

• The entrypoint script currently relies on bash... this is obviously limited.

  #32 opened 8 years ago by zancas
  0

• A Complete Flow for `containenv init` on an extant project needs to be implemented.

  #30 opened 8 years ago by zancas
  0

• Need to integrate Travis CI with our slack team. It should have its own channel.

  #20 opened 8 years ago by zancas
  0

• There are several different types of dependencies that should be transparently managed.

  #3 opened 8 years ago by zancas
  4

• We need to sync on the current state of the interface and the development process

  #6 opened 8 years ago by zancas
  6

• The project needs a rudimentary CI (.travis.yaml) that runs flake8, pep8, etc..

  #17 opened 8 years ago by zancas
  0

• possibly promote exceptions to their own module.

  #14 opened 8 years ago by zancas
  0

• We want an onslaught badge

  #23 opened 8 years ago by zancas
  0

• Dockerfile

  #12 opened 8 years ago by jputrino
  2

• We need a high degree of assurance that the contained env properly interacts with the host FS.

  #5 opened 8 years ago by zancas
  0

• Docs

  #22 opened 8 years ago by jputrino
  0

• README

  #21 opened 8 years ago by jputrino
  0

• We wish to use testenv-derived display output.

  #16 opened 8 years ago by zancas
  0

• Common functionality needs to be promoted to a convenient location for tools

  #9 opened 8 years ago by zancas
  0

• containenv needs to support multiple containerization technologies

  #8 opened 8 years ago by zancas
  0