Plek is the glue between serverless services like ZEIT Now and GitHub, improving your continuous deployment workflow. Serverless and continuous deployment go together like bread and butter, Plek accentuates on this with a defined flow and feedback to GitHub. Every deployment status is reported to GitHub and a domain is assigned based on the branch. On the main branch the deployment goes directly to your domain and for pull requests a subdomain is used to preview the changes. Resulting in a quick feedback loop where it is easy for everybody involved with a project to view changes.
Does this sound like the recently announced ZEIT Now for GitHub? Yes it does, these solutions certainly overlap. When releasing Plek this wasn't applicable since Now for GitHub got released about three weeks later. They serve different use-cases though because Plek runs from your CI as a CLI tool. This is a difference in responsibility, you have control over how and when Plek runs. This flexibility comes in handy for scenarios such as:
- deploying monorepos, a repository that contains multiple packages or projects;
- running tests before deploying;
- using private npm packages in a Node.js project.
Whereas Now for GitHub is limited but easier to run because it runs from Now’s environment, meaning no CI setup is needed but also limits the possibilities. So if the Now to GitHub pipeline is all you need Now’s integration works fine. But if you want more, use Plek, did I mention it is open source too? Check it out at voorhoede/plek.
Serverless is a cost-effective and easy way to deploy apps, deploy code and let services take care of it. With this power, continuous deployment becomes a natural way of going live. ZEIT Now and Fly integration from your CI is just a command away with
plek now and