How it works The Slack integration works by sending a notification, to a Slack channel of your choice, every time Squash receives one of the following events: ERROR: error during the startup process of your deployments. Any errors that prevent Squash from getting a success response (such as build errors or timeouts) will trigger a notification. SUCCESS: this will be triggered when Squash receives ...

When the Assets Storage is enabled Squash will automatically add a new /assets/ mount point for all deployments within the repository. You can upload up to 100GB of data in this folder (additional charges apply, check out the pricing page). How to enable the Assets Storage Step 1 Go to the Squash Admin page and then click on Settings -> Repositories Step 2 Pick a repository and click on “Settings”...

Available VM sizes Click here for a complete list of the available VM types, including memory, storage and CPU. Changing VM sizes You can configure the right amount of memory, vCPU and storage to tailor your needs. Every application is different and Squash gives you flexibility to change these settings in multiple levels. Account Level This gives you a default VM size that is used across all repos...

A Squash deployment consists of a at least one unique virtual machine associated with a branch of code. By default, if you have only one unique web app within a repository, Squash will commission one virtual machine for each branch of code. You can commission as many virtual machines as you like within your plan's concurrency limit and limit of hours. Squash also supports running multiple virtual ...

Basic HTTP Authentication is a great and easy way to add a username/password gate to your deployments and make sure that only authorized personal can access them. There are current two ways to define Basic Auth credentials in Squash. Squash Interface When Basic Auth is defined through the Squash interface your deployments will only start after the credentials are successfully checked within Squash...

Squash supports a special syntax for dealing with any level of subdomains. This allows your application subdomains to still work with SSL/HTTPS without the need of separate SSL certificates. If you are curious, Squash also supports custom domains & custom/Free SSL. Here is how it works: Squash translates any double dashes (--) within the hostname and converts them to subdomains when passing the re...

This feature is currently not available for accounts under the free plan. For more details please go to our plans page. You can add one or more custom domains to your account and we will add a Free SSL certificate for each domain. Custom domains will look like this: Squash supports a maximum of one domain per unique application or Dockerfile/docker-compose-file. Once you decide and purchase your c...

Once a deployment is up and running Squash can automatically notify when there are new commits pushed to branch associated with your deployment. You can restart the deployment anytime to get the latest version. This is how the notification UI looks like, it will show up within the deployment URL itself (where you have your app running) at the top of the page. How to enable the notification of code...

Squash offers multiple ways to deploy applications based on a microservices architecture. Once you decide what integration method to use (YAML file, Docker or Kubernetes) you can then have Squash to automatically create deployments for each branch of code and integrate with Pull/Merge Requests. YAML file For apps without Docker you can define multiple applications and services within the Squash YA...

Squash automatically adds a comment on each Pull Request with a unique URL per branch of code. When you click on such URLs Squash will create a new virtual machine and will immediately display a loading page like this: and then it will start deploying your branch's code. When your application build process is finished, Squash will look for a success response and will then automatically start routi...

The auto shutdown policies are a great way to eliminate server waste, allowing your Squash deployments to stay active only when you need them, and no more. Below are listed several policies you can use to fit your needs. Date & Time Policy Deployments with this policy will automatically terminate at a given date and time. How to define this policy from the Squash deployment settings page: Click on...

The Deployment Cache (DC) is a good way to speed up the build process of deployments. This feature is enabled by default on all repositories. Squash generates a cache snapshot for the following types of apps, across all branches in a repository: A Squash YAML file, in case you are not using Docker Each unique Dockerfile or docker-compose file This is done by keeping a md5sum reference of each file...

Note: currently this feature is not available for Kubernetes based deployments. We will be adding this soon. You can enable the persistent storage feature when you need to keep your data intact between deployment restarts. This feature comes with a few important details: Squash automatically skips the application build process when persistent storage is enabled. This is to avoid re-creating the co...

This feature is currently not available for accounts under the free plan. For more details please go to our plans page. Squash can automatically start new deployments based on each commit and act similar to a Continuous Integration (CI) system. This gives you the power to check if a Squash build is successful and returning a success response for a given commit. You may also automatically run speci...

This feature is currently not available for accounts under the free plan. For more details please go to our plans page. Squash supports linking apps/microservices from multiple code repositories. This facilitates the deployment of complex apps with multiple microservices living in separate repositories. You may also define dependencies such as a database service running on its own VM or any type o...

Squash has native support for Kubernetes (k8s). Currently this option is only available through the Squash YAML file. In order to get started you need to add the deployment_type: kubernetes field in the Squash YAML file, for all applications that are Kubernetes based. Then use our Kubernetes specific YAML file fields to customize your applications to fit your needs. Below you will find some sample...

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 one or more services within the Squash YAML file, see examples below. Each non-HTTP ...

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 or more microservi...

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 using any framework. Automatically ship changes to...

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 use the latest image for caching purposes. Squash still builds a new image from s...