<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Selwyn</title>
    <description>The latest articles on DEV Community by Selwyn (@siilwyn).</description>
    <link>https://dev.to/siilwyn</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F112480%2Ffecf8cc6-86a7-4d9e-a74f-3ff7b73ab42a.jpeg</url>
      <title>DEV Community: Selwyn</title>
      <link>https://dev.to/siilwyn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/siilwyn"/>
    <language>en</language>
    <item>
      <title>Introducing Plek 3.0</title>
      <dc:creator>Selwyn</dc:creator>
      <pubDate>Tue, 06 Nov 2018 13:07:07 +0000</pubDate>
      <link>https://dev.to/siilwyn/introducing-plek-30-5fo5</link>
      <guid>https://dev.to/siilwyn/introducing-plek-30-5fo5</guid>
      <description>&lt;p&gt;&lt;a href="http://plek.now.sh/"&gt;Plek&lt;/a&gt; is the glue between serverless services like &lt;a href="https://zeit.co/now"&gt;ZEIT Now&lt;/a&gt; and GitHub, improving your continuous deployment workflow. &lt;a href="https://martinfowler.com/articles/serverless.html"&gt;Serverless&lt;/a&gt; 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.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--7uIedbEN--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/smst1psrnmx8bdcz2tdz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--7uIedbEN--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/smst1psrnmx8bdcz2tdz.png" alt="GitHub PR checks"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Flow
&lt;/h2&gt;

&lt;p&gt;Does this sound like the recently announced &lt;a href="https://zeit.co/docs/integrations/now-for-github"&gt;ZEIT Now for GitHub&lt;/a&gt;? 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:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;deploying monorepos, a repository that contains multiple packages or projects;&lt;/li&gt;
&lt;li&gt;running tests before deploying;&lt;/li&gt;
&lt;li&gt;using private npm packages in a Node.js project.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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 &lt;strong&gt;&lt;a href="https://github.com/voorhoede/plek/"&gt;voorhoede/plek&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fly
&lt;/h2&gt;

&lt;p&gt;Plek is CI and service agnostic with the goal to support multiple serverless services and git platforms like GitLab. To prove that Plek is super flexible, we just released Plek 3.0 adding &lt;a href="https://fly.io/"&gt;Fly&lt;/a&gt; as a service, more to come! Fly is an open source JavaScript runtime that gives you the power to create your own programmable CDN. With this power you can deploy anything from load balancers to static websites, combined with Plek it is easily deployed and tested.&lt;/p&gt;

&lt;p&gt;&lt;iframe src="https://player.vimeo.com/video/299021064" width="710" height="399"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;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 &lt;code&gt;plek now&lt;/code&gt; and &lt;code&gt;plek fly&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://plek.now.sh/guide/getting-started.html"&gt;&lt;br&gt;
  &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--xHPP2uHC--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/8644whlikhn311ko17fu.png" alt="Let's get started"&gt;&lt;br&gt;
&lt;/a&gt;&lt;/p&gt;

</description>
      <category>serverless</category>
      <category>ci</category>
      <category>cd</category>
      <category>github</category>
    </item>
  </channel>
</rss>
