Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • rt_decloud rt_decloud
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

En prévision de l'arrivée de la forge institutionnelle INRAE, nous vous invitons à créer vos nouveaux projets sur la forge MIA.

  • umr-tetisumr-tetis
  • rt_decloudrt_decloud
  • Issues
  • #2
Something went wrong while setting issue due date.
Closed
Open
Issue created 3 years ago by Narcon Nicolas@nicolas.narconMaintainer

Ready-to-use docker

Closed

Ready-to-use docker

Should we pip install . decloud in the docker ? This would enable to import decloud from anywhere without having to clone the repo.

If so, how to make the production/ scripts available?

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Related merge requests

    1

    When this merge request is accepted, this issue will be closed automatically.

    • Resolve "Ready-to-use docker"
      !2

    Activity


    • Narcon Nicolas
      Narcon Nicolas @nicolas.narcon · 3 years ago
      Author Maintainer

      To make the production/ scripts available, we could modify the setup.py by adding:

      entry_points={
          'production_scripts': [
              'crga_processor=decloud.production.crga_processor:main',
              ...
          ],
      }

      Then, it would enable to use the command crga_processor instead of python3 crga_processor.py

    • Narcon Nicolas created branch 2-ready-to-use-docker to address this issue 3 years ago

      created branch 2-ready-to-use-docker to address this issue

    • Narcon Nicolas mentioned in merge request !2 (merged) 3 years ago

      mentioned in merge request !2 (merged)

    • Cresson Remi closed via commit 93d55c73 3 years ago

      closed via commit 93d55c73

    Please register or sign in to reply
    0 Assignees
    None
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets