During Studio installation on your local development machine, a new directory named
replicated is created in your home directory. Once your license is activated, Replicated Studio will set up the most recent release and save it to
~/replicated/current.yaml. Any time this file is updated and saved, Replicated Studio will create a new release using the next available sequence number. To start you’ll probably want to copy and paste your most recent yaml as the downloading process often adds in default
From there you can use your favorite editor locally (like Atom, Visual Studio Code, Vim, or Emacs) and saved changes will trigger new updates available to your development server.
Note: In the directory
~/replicated/releases/ you can view a copy of each release Replicated Studio has created along the way.
If you supply an invalid yaml file that isn’t recognized as a valid update in the on-prem UI, you can simply delete the invalid release iteration from the local directory
~/replicated/releases and save a new version of
Applying updates to the dev server
After you have saved your
current.yaml changes, you can navigate to your on-prem Admin Console (
https://<YOUR SERVER ADDRESS>:8800) and click the
Check for updates button to see your new release.
As well as being able to iterate on your application YAML, you can also use Studio to iterate on your Docker images. This simplifies the development workflow when you need to make changes to your code base to support on-prem deployments.
To do this, rebuild your Docker images on your Studio server reusing the existing tags. Once you restart the application from the on-prem Admin Console (
https://<YOUR SERVER ADDRESS>:8800) or CLI, your updated images will be used by Replicated.
Note: When iterating on Docker images in Studio, referencing local Docker images using the
latest tag is not supported. Replicated will re-pull any images with the
latest tag, thus overwriting any changes you are making locally.
The logs from Replicated Studio display any lint or syntax issues detected in your application yaml. You can also view all interactions the on-prem Replicated has with the Studio API.
You can follow these logs in real time using:
docker logs -f studio