Squash supports the native Docker Secrets functionality. This allows keeping any sensitive environment variables out of the Docker image. Using this feature is simple and requires just a few steps that need to be added within the Squash YAML file. The build_options field is required and the –secrets flag must be present. Example: build_options: –no-cache

There are two easy ways to greatly speed up the build and startup time of web apps in Squash. Besides improving the user experience, fast startup times allow you to reduce the expiration time of your deployments, which will lead to significant cost savings. Using the Deployment Cache First check if the Deployment Cache feature

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running Web apps written in Go is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavour of

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running TypeScript based apps is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a major

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running Web apps on any stack is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running Ruby based apps is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a major

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running Java based apps is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a major

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running PHP based apps is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a major

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running NodeJS based apps is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a major

If you are using Docker or Kubernetes you can check specific instructions for these at the bottom of this page. Building and running Python based apps is quite straightforward in Squash. There are basically three elements to accomplish this: Pick the base OS image from Docker Hub, this is usually a flavor of a major

Squash automatically pulls your public keys from either GitHub/Bitbucket/GitLab allowing you to SSH to any Squash instance without any additional setup. You may also upload public keys directly into Squash. How to SSH to a Squash instance Every Squash deployment has a SSH endpoint allowing you to debug complex issues and perform updates to your

Squash has  a built-in Docker Registry that you can use to easily store and retrieve Docker images from your applications. How it works When Squash builds a new version of your app it will automatically create a new image and push it to the registry, if the build is successful. New subsequent builds will automatically

This feature is currently not available for accounts under the free plan. For more details please go to our plans page. Squash allows you to define multiple pipelines to handle the most complex use cases for executing automated scripts and even shipping code to production environments. Use cases Run all your unit tests, regression/functional tests

Tech Stack Examples Python NodeJS PHP Ruby Java TypeScript Go Basic example – using a Dockerfile For this first example we have a web app defined in a Dockerfile, this web app has an HTTP service running on port 3000 and we are using the port_forwarding field to properly tell Squash to route traffic to

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