Customizing Deployments

Sample YAML file configurations

Avatar

squashlabs, December 2, 2019

Docker & Docker Compose configurations Basic example Here you have a web app defined in a Dockerfile, this web app has an HTTP service running on port 3000. deployments: MyApp: filename: ./src/Dockerfile context_path: ./src port_forwarding: # Squash by default expects an HTTP service running on port 80. # For this example the HTTP service is

Read more

Multi-repository applications

Avatar

squashlabs, December 2, 2019

Squash supports applications made of several microservices defined within separate repositories. There are currently three ways to get such apps running in Squash: Using the deployment dependencies feature. Squash creates a unique VM for each independent repository and attach them all together through environment variables. This requires very little setup. You may also share one

Read more

Non-HTTP based deployments

Avatar

squashlabs, August 30, 2019

Squash supports launching service based deployments without an HTTP end point. This is helpful if you want to spin up a read-only database or any services that you want to share with one or more feature deployments. This is currently only supported within the Squash YAML file. How it works First you need to define

Read more