Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
hotpotato
hotpotato
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 5
    • Merge Requests 5
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Hot-Potato
  • hotpotatohotpotato
  • Issues
  • #123

Closed
Open
Opened Dec 03, 2019 by Zac Pullar-Strecker@zacpsMaintainer

Hotpotato CLI command requires a pipenv environment

To use the hotpotato command inside the hotpotato-dev container you must have installed the pipenv environment outside of the container.

This is because the container mounts the code directory as a volume and the hotpotato.egg-info subdirectory is needed for the entrypoint to be found.

Workaround is to install the pipenv environment, but ideally the container should be configured so that this isn't required.

@rhysmd

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
v0.9.4
Milestone
v0.9.4
Assign milestone
Time tracking
None
Due date
None
Reference: Hot-Potato/hotpotato#123