Previously, the Tiltfile was hard-wired to Jeff's development
environment on the k2 cluster on-prem. This doesn't work for other
contributors.
This patch fixes the problem by re-using the Try Holos Locally
documentation to create a local development enironment. This has a
number of benefits. The evaluation documentation will be kept up to
date because it doubles as our development environment. Developing
locally is preferrable to developing in a remote cluster. Hostnames and
URL's can be constant, e.g. https://app.holos.localhost/ for local dev
and https://app.holos.run/ for production. We don't need to push to a
remote container registry, k3d has a local registry built in that works
with Tilt.
The only difference presently between evaluation and development when
following the local/k3d doc is the addition of a local registry.
Previously, the Tiltfile was hard-wired to Jeff's development environment on the k2 cluster on-prem. This doesn't work for other contributors.
This patch fixes the problem by re-using the Try Holos Locally documentation to create a local development enironment. This has a number of benefits. The evaluation documentation will be kept up to date because it doubles as our development environment. Developing locally is preferrable to developing in a remote cluster. Hostnames and URL's can be constant, e.g. https://app.holos.localhost/ for local dev and https://app.holos.run/ for production. We don't need to push to a remote container registry, k3d has a local registry built in that works with Tilt.
The only difference presently between evaluation and development when following the local/k3d doc is the addition of a local registry.
With this patch holos starts up and is accessible at https://app.holos.localhost/