You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 1, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/decisions/0004-backends-depend-on-frontends.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ Consequences
60
60
* An email and Slack message will be sent out to explain these changes and how we anticipate that they will impact developer workflows. The email will explain that if a micro-frontend is required to simulate common user story in the default configuration, then that frontend should be devstack, and should be automatically started by the relevant backend using ``depends_on``.
61
61
62
62
63
-
.. _documentation in frontend-build: https://github.com/edx/frontend-build#local-module-configuration-for-webpack
63
+
.. _documentation in frontend-build: https://github.com/openedx/frontend-build#local-module-configuration-for-webpack
Copy file name to clipboardExpand all lines: docs/decisions/0005-frontend-package-mounts.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Current SOA: Local packages for frontends
34
34
35
35
Unfortunately, this flow is currently *not* an option for frontend services (i.e., micro-frontends) when they're run via devstack. This was probably not an intentional omission; frontend services were added to devstack in a somewhat ad-hoc way, and the local-package workflow was probably overlooked.
36
36
37
-
There is, however, an established strategy for using local packages when running frontends *outside* of devstack. This stategy is described in the `frontend-build documentation <https://github.com/edx/frontend-build#local-module-configuration-for-webpack>`_. Essentially, frontend package respositories can be placed anywhere in the host system, and each frontend's ``module.config.js`` can be pointed at those local respositories using a path relative to the frontend itself. For example:
37
+
There is, however, an established strategy for using local packages when running frontends *outside* of devstack. This stategy is described in the `frontend-build documentation <https://github.com/openedx/frontend-build#local-module-configuration-for-webpack>`_. Essentially, frontend package respositories can be placed anywhere in the host system, and each frontend's ``module.config.js`` can be pointed at those local respositories using a path relative to the frontend itself. For example:
38
38
39
39
* A frontend dev has ``frontend-app-profile`` within their home folder (``~``).
40
40
* They would like to run a modified version of Paragon, located at ``~/paragon``.
@@ -108,4 +108,4 @@ A more radical alternative would be to explicitly mount certain local frontend p
108
108
109
109
This approach would have been the most compatible with the existing local frontend package strategy, but it would sharply differ from devstack's backend package strategy.
110
110
111
-
For reference, here is a draft implementation of this rejected approach: https://github.com/edx/devstack/pull/795.
111
+
For reference, here is a draft implementation of this rejected approach: https://github.com/openedx/devstack/pull/795.
- ``COMPOSE_PROJECT_NAME=docker-compose.container`` (i.e.: "devstack-juniper.master"; appropriate docker-compose container project for devstack multiple release (same machine); ensures specific Docker containers get used based on release name; Ref: https://github.com/edx/devstack/pull/532)
53
+
- ``COMPOSE_PROJECT_NAME=docker-compose.container`` (i.e.: "devstack-juniper.master"; appropriate docker-compose container project for devstack multiple release (same machine); ensures specific Docker containers get used based on release name; Ref: https://github.com/openedx/devstack/pull/532)
0 commit comments