Customizing Deployments

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

Read more

Pre-seeded databases (dev dbs)

squashlabs, April 23, 2019

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,

Read more

Repos with Multiple Apps

squashlabs, April 16, 2019

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

Read more