This tutorial will show you how to take an example microservice from source code to a Kubernetes cluster using Wercker, Google Container Engine (GKE) and Google Container Registry (GCR).
Editor’s note: Today’s guest post is by De Ville Weppenaar, a developer at Ad Dynamo, showing how to Automate your Firebase deploy with Wercker
At Wercker we need to run scheduled jobs on our Kubernetes cluster. Since Kubernetes’ answer to cron (ScheduledJobs) isn’t quite production ready yet.
We’re excited to announce the launch of Wercker Workflows, an important step toward solving the key automation challenges in CI/CD when deploying to cloud native architectures consisting of container registries and schedulers.
The goal of this guide is to get you comfortable automating your deployments to a Digital Ocean server using the wercker platform.
Amazon EC2 Container Service (ECS) is a container management service that allows you to run, stop and manage containers on a cluster of Amazon EC2 instances.
In this post we’ll discuss how to deploy a project consisting of two services to Mesosphere, or more specifically a running Marathon instance.
Docker is a popular product for running and distributing containerized applications, and Dockerfiles are a common way of constructing those containers. Unfortunately, Dockerfiles and the underlying assumptions they base their philosophy on are anti-patterns for exactly the kind of use cases Docker wants to solve.
Writing tests is a staple in providing quality code. Code of all varieties can benefit heavily from having an extensive test suite. Only by having automated tests in place can you guarantee that the assumptions you are making about your code are true.
Build, test and deploy like never before with the power of Wercker