Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

Implicitly mount and install edx-platform packages #177

Closed
kdmccormick opened this issue Aug 18, 2023 · 1 comment · Fixed by overhangio/tutor#915
Closed

Implicitly mount and install edx-platform packages #177

kdmccormick opened this issue Aug 18, 2023 · 1 comment · Fixed by overhangio/tutor#915
Assignees

Comments

@kdmccormick
Copy link
Collaborator

kdmccormick commented Aug 18, 2023

As discussed at DevX, we want to:

  • implicitly mount repos into edx-platform containers & build context based on some prefixes (platform-plugin-*, xblock-*, platform-lib-*).
  • tell people about those prefixes so they know the benefit of using them.
  • install the packages in the dockerfile, something like this (not tested):
    • RUN bash -c 'for p in $(ls /openedx/packages) ; do "pip install -e /openedx/packages/$p" ; done'
  • possibly deprecate the current method for installing packages? (/openedx/requirements + private.txt).

We want full the workflow to look something like:

# for packages following our naming conventions:
tutor mounts add path/to/xblock-foo

# for other packages:
mv path/to/bar-xblock path/to/xblock-bar
tutor mounts add path/to/xblock-bar

tutor images build openedx-dev
tutor dev reboot
@kdmccormick
Copy link
Collaborator Author

I wanted this feature in order to help me work on a Studio project, so I have a very hacky personal implementation of it going in kdmccormick/tutor#36. I currently have no plans to clean that up for merge, but I'll post here again if that changes.

@regisb regisb changed the title Implictly mount and install edx-platform packages Implicitly mount and install edx-platform packages Oct 9, 2023
regisb added a commit to overhangio/tutor that referenced this issue Oct 9, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Oct 9, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Nov 14, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Nov 20, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Nov 22, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Nov 30, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Dec 10, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Dec 10, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Dec 10, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Dec 10, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Dec 10, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
regisb added a commit to overhangio/tutor that referenced this issue Dec 10, 2023
These changes make to possible to run:

    tutor mounts add /path/to/my-xblock

The xblock directory with then be auto-magically bind-mounted in the
"openedx" image at build time, and the lms*/cms* containers at run time.

This makes it effectively possible to work as a developer on
edx-platform requirements.

We take the opportunity to move some openedx-specific code to a
dedicated module.

Close openedx-unsupported/wg-developer-experience#177
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants