Installation is done for you as soon as you open the terminal within VSCode.
All environment variables and secrets are loaded via Envkey. To get access to your Envkey account, please follow this steps:
If you need help setting up your environment please contact a Devop!
devowl.io Gmbh
organization within Envkey.env
in the root of our cloned Git repository (do not save the file until we explicitely request this!).env-default
into the .env
fileENVKEY
secret, which allows us to access the Envkey vault:Monorepo (Global)
in Envkey UIENVKEYs
Local Development Keys
and create your key with name ci-runner-x.owlsrv.de
(replace x
with your runner number!)ENVKEY
secret to your .env
file (make sure to remove the ENVKEY=
from the copied content to avoid something like ENVKEY_REAL_COMMERCE=ENVKEY=
)ENVKEY_
variables within your .env
for the proper app in Envkey, e.g. ENVKEY_REAL_COMMERCE
belongs to the Real Commerce
app.Monorepo (Global)
in Envkey UIEnvironments
Development
environment click the branch iconENVIRONMENT_BASE_HOSTNAME
with value ci-runner-x.owlsrv.de
(replace x
with your runner number!).env
fileOpen the Traefik monitor at port 8080
to see the domains of all services (e.g. http://ci-runner-8.owlsrv.de:8080/).
Some often-used commands are provided via the native VSCode tasks view. Just open the Command Pallete
, delete the >
character and type in task
(with space!). All other commands are available in the package.json#scripts
section.
Each domain prefix must be prefixed to the FQDN of the host running the containers (e.g. host ci-runner-x.owlsrv.de
and domain prefix commerce
becomes commerce.ci-runner-x.owlsrv.de
).
Description | Environment | Docker service | Domain prefix |
---|---|---|---|
WordPress Plugins | Development | wordpress |
wordpress. |
Real Product Manager (Backend) | Development | real_product_manager |
license. |
Real Commerce (Backend) | Development | real_commerce |
commerce. |
Real Cookie Banner (Backend) | Development | real_cookie_banner_backend |
rcb. |
phpMyAdmin | Development | phpmyadmin |
pma. |
phpRedisAdmin | Development | phpredisadmin |
pra. |
Package type | Allow side effects* | Description |
---|---|---|
dev-packages |
No | Packages, which are needed only for development purposes within this monorepo |
api-packages |
No | API interfaces and types, which can be consumed by backends and frontends |
backend-packages |
No | Logic, which can be consumed by backends |
wordpress-packages |
No | WordPress-specific packages with PHP and TS coding which can be consumed by wordpress-plugins |
frontend-packages |
No | Logic, which can be consumed by different types of frontends in different ecosystems |
isomorphic-packages |
No | Logic, which can be consumed anywhere and independent of the ecosystem (e.g. package provides logic for PHP and JavaScript) with feature-parity |
frontends |
Yes | Dockerized frontends (e.g. create-react-app ) |
backends |
Yes | Dockerized backend services |
wordpress-plugins |
Yes | WordPress-specific plugins with PHP and TS coding |
* Side effects: A side-effect free file does not execute code at import time, instead it only exports types, interfaces and reusable components. A side effect e.g. is starting a webserver in the main file.
Generated using TypeDoc