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

Back to the Squash YAML file page. Supported YAML fields The YAML fields below are supported on Kubernetes based deployments only. deployment_type This controls the deployment type: Docker or Kubernetes Mandatory field: Yes for Kubernetes. You need to set this value as “kubernetes” Data Type: Choices: kubernetes, docker Default value: docker For this example we

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

Squash has native support for self-hosted GitLab instances, all Squash features are available in this integration. To get start first go to the Squash Sign up page, click on “Signup with GitLab” and then “GitLab Self-hosted” in the next page. Then click on the highlighted link to setup your GitLab access: The next step is

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

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

Please note that the steps below are only required for private repositories.  By default Squash uses OAuth access tokens from the hosted Version Control System provider (GitHub, Bitbucket or GitLab) in order to fetch a branch’s code during a Squash deployment. We do this in order to keep the amount of permissions on each provider

Squash makes it very easy to seed development databases. You can use your own sanitized data set or even clone production dumps (although in some cases this might not be recommend, see below). The way it works is based on importing a development db dump from any SQL or non-SQL database engines (MySQL, PostgreSQL, MongoDB,

Back to the Squash YAML file page. The YAML fields below are supported on YAML based (non-Docker) deployments only. build_steps Defines a list of steps that should be executed in order to prepare the environment. Such steps may include package installations, DB initialization and should not include commands that start any kind of services. It’s

Back to the Squash YAML file page. The Docker based build process Here is a sample of a Squash YAML file with two applications within the same repo. Each application requires  its own Dockerfile or docker-compose file. deployments: CRM: filename: ./src/crm/Dockerfile context_path: ./src vm_size: 1GB CoreApp: filename: ./src/coreapp/docker-compose.yml context_path: ./src vm_size: 2GB Supported YAML fields

Back to the Squash YAML file page. The YAML fields below are supported on any application type (Docker or non-Docker based). allow_public_ports This will open in the firewall one or more ports for external access. Squash by default restricts external access to all ports running on deployment VMs except the SSH port and ports used

Squash supports multiple applications within the same repository. You can test each app independently off its own virtual machine. You can also define custom PR comments with unique deployment links for each application. This works for apps based on Docker or without it (Squash YAML file based). Example using Docker/docker-compose The Squash YAML file sample

You can define custom actions in the Squash YAML file. These are custom commands that will be executed inside your application’s container or within the host VM itself. When you define a custom action it will appear in the Deployment settings page, as a new item within the “Actions” dropdown. This is an easy way

Host OS and installed packages The host virtual machine where we deploy your Docker containers comes with an absolute minimum list of handy tools. These are not meant to be extensive since you can fully customize the environment within a Docker container to fit your needs. Host environment details: Operating System: Amazon Linux 2 (CentOS

Squash only requests the absolutely minimum set of permissions on GitLab. We support both GitLab Cloud and GitLab Self-hosted. GitLab Self-Hosted Setup Please follow the steps on this page for GitLab Self-Hosted. GitLab Cloud When you signup you will be prompted to the following screens: Oauth This is the standard GitLab authorization page requesting your