![]() ![]() Here is a sample of how to define a private Docker image in the YAML file, for this example we have previously defined a REGISTRY_PASSWORD environment variable within the Squash interface. This is a great solution If you have multiple Dockerfiles within the same repository or simply want more flexibility You can also specify the access information for private Docker images in the Squash YAML file. Using Private Docker images in the Squash YAML fle For repos with only one Dockerfile or docker-compose file you may define the image details in the Squash Deployment UI as follows, this works for both Dockerfiles or docker-compose files: # variables from the Squash interface and use them here. # these are built-in environment variables that you can pass to the # For this example the HTTP service is listening to port 3000. # Squash by default expects an HTTP service running on port 80. squash.yml file example of how the example above would look like: deployments: You can configure Squash in such a way that when you create a Pull Request you will get a comment like this:Īnd because each of the Squash URLs above are unique, each of them will trigger separate deployments running off their own virtual machines.Ĭurrently you must use the Squash YAM file to define such deployments. And each application will receive their own unique URL running on its own virtual machine.įor example, let’s explore a scenario where a repository has the following files (let’s assume the branch name is “lib_upgrades”): For such cases each Dockerfile or docker-compose file is considered a unique application. Squash supports multiple Dockerfiles or docker-compose files within the same repository, on any path. ![]() Multiple Dockerfiles or docker-compose files ![]() You may define custom Dockerfile locations in the Squash YAML file. Venzl docker squash code#Automatic Docker detectionīy default we will attempt to detect a Dockerfile or docker-compose file at the root path of your application code as follows: The best way to start testing your first deployments is by using the Squash deployment interface, this interface will guide you through a few steps and questions in order to get your deployment up and running. Squash has native & first-class support for Dockerfiles and Docker-compose. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |