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 has been archived by the owner on May 10, 2023. It is now read-only.
Currently the Umbrel development VM has an environment that very closely mirrors the production Umbrel OS environment.
This is great for checking changes are likely to work in Umbrel OS but it slows down development since it means Docker images need to be rebuilt and services restarted after each change.
It would be great if by default the dev VM used the development servers for development. So instead of building images and running services it just runs the npm dev scripts and benefits from live reload webservers etc.
We should still support the production-like docker environment too but we should be able to switch between them with something like umbrel-dev env production/umbrel-dev env development.
This command would handle automatically rebuilding the images or starting the dev server to reflect the latest changes.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the Umbrel development VM has an environment that very closely mirrors the production Umbrel OS environment.
This is great for checking changes are likely to work in Umbrel OS but it slows down development since it means Docker images need to be rebuilt and services restarted after each change.
It would be great if by default the dev VM used the development servers for development. So instead of building images and running services it just runs the npm dev scripts and benefits from live reload webservers etc.
We should still support the production-like docker environment too but we should be able to switch between them with something like
umbrel-dev env production
/umbrel-dev env development
.This command would handle automatically rebuilding the images or starting the dev server to reflect the latest changes.
The text was updated successfully, but these errors were encountered: