Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Issues
  • #106

Closed
Open
Opened Sep 06, 2018 by Lukas Riedel@lriedelOwner

Move 'dorie' script into Python package

Description

The dorie script for running all user tasks of DORiE is currently separated from the remaining Python environment. As implemented in https://ts-gitlab.iup.uni-heidelberg.de/utopia/utopia, we can also install it as a script of the Python environment. We can then access it directly after entering the virtualenv. This relaxes the requirement of fiddling with the PATH variable. It also serves as preparation for future additions (regarding especially #86 (closed)), where Python scripts will be executed on input files before DORiE can run. Once inside the virtualenv, all required Python packages for these tasks are readily installed.

The workflow with virtualenv is as follows:

# activate virtualenv
source <path/to>dorie/build-cmake/activate
cd <some/where>
# dorie command always available
dorie create
dorie run
# deactivate virtualenv
deactivate

Proposal

  • Move the dorie script into python/dorie/wrapper/ and install it with the Python modules.
    • Modify dorie wrapper directory for tests
    • Modify CI scripts
  • Change the documentation and README.md: How to use virtualenv.
  • Modify Docker application: Entrypoint will be the activated virtualenv. Users can then issue multiple commands from within the same container.

How to test the implementation?

  • Pipeline still works.
  • Verify that usage of Docker application works.

Related issues

See #103 (closed)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#106