<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tim Ermilov on Medium]]></title>
        <description><![CDATA[Stories by Tim Ermilov on Medium]]></description>
        <link>https://medium.com/@yamalight?source=rss-94ac54b64fc4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*srKjH77vDwD3_pM91f2ErQ.jpeg</url>
            <title>Stories by Tim Ermilov on Medium</title>
            <link>https://medium.com/@yamalight?source=rss-94ac54b64fc4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:11:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yamalight/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing Exoframe 3.0 — easy complex deployments & Docker Swarm support]]></title>
            <link>https://medium.com/hackernoon/announcing-exoframe-3-0-easy-complex-deployments-docker-swarm-support-c8ab6f4e05b2?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8ab6f4e05b2</guid>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Wed, 23 May 2018 19:15:55 GMT</pubDate>
            <atom:updated>2018-05-23T19:15:55.422Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<blockquote>Exoframe is a self-hosted tool that allows simple one-command deployments using Docker. <br>If you are not familiar with it — you can find out more in the <a href="https://hackernoon.com/announcing-exoframe-1-0-simple-docker-deployment-tool-59bde252139d">article on initial release</a> and the <a href="https://github.com/exoframejs/exoframe">project repository</a>.</blockquote><p>I am happy to announce the release of <a href="https://github.com/exoframejs/exoframe">Exoframe</a> 3.0!<br>Two major highlights for this release are complex deployment recipes and Docker Swarm support.</p><h3>Deployment recipes</h3><p>Docker allows to deploy complex systems using docker-compose files, but they are limited due to Docker constraints — you cannot wait for services to become available, cannot execute post-init scripts, it might be hard to prepare configs, etc. <br>There are of course workarounds for some of those things — <a href="https://docs.docker.com/compose/startup-order/">some of them</a> are mentioned in the official Docker docs, others <a href="https://github.com/docker/compose/issues/1809">discussed in github issues</a>.</p><p>Exoframe aims to address those problems with “recipes” feature. It provides a way to run third-party complex deployment recipes (that are essentially javascript code that has direct access to Docker daemon).<br>Those recipes provide a quick and easy way to deploy complex projects in one command.</p><p>The way recipe work is pretty straightforward:</p><ol><li>Developer <a href="https://github.com/exoframejs/exoframe/blob/master/docs/RecipesGuide.md">writes an exoframe recipe</a> and publishes it on npm</li><li>User installs and configures Exoframe on server and locally</li><li>User executes recipe with exoframe setup recipe-name where <em>recipe-name </em>is the package name from npm</li><li>Exoframe pulls the recipe from npm and presents a set of developer-defined questions to the user (see screenshot below)</li><li>Once the user answers the questions, Exoframe server executes the recipe code and sets up the system in a required way</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UMJ0dUkAr1VeaJmoNN3q6Q.png" /><figcaption>Example wordpress recipe execution</figcaption></figure><p>As an example recipe, you can deploy Wordpress backed by MariaDB along with PHPMyAdmin by simply executing exoframe setup exoframe-recipe-mysql and answering a set of simple questions (screenshot above).</p><p>If that doesn’t look convincing — I don’t blame you, that deployment is pretty simple and can be easily done with one docker-compose.yml :)<br>Here’s an example of something a bit more complex — <a href="https://github.com/hobbit-project/platform">HOBBIT platform</a>. You can find the setup guide for it <a href="https://github.com/hobbit-project/platform#hobbit-platform">here</a> — as you can see, it’s not exactly simple and there’s more to it than just running docker-compose up. And here’s how the setup looks with <a href="https://github.com/hobbit-project/exoframe-recipe-hobbit">Exoframe recipe</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PkPbJ-H_auXb0jCBKNPzDg.png" /><figcaption>Example HOBBIT project recipe execution</figcaption></figure><p>Looks exciting? Give it a try! And don’t forget to share all the awesome recipes you build!</p><h3>Docker Swarm support</h3><p>A slightly smaller new feature in 3.0 (but something that’s been frequently requested by the community) is Docker Swarm support.<br>Exoframe can now work in Swarm environments and allows you to deploy your services to Swarm in exactly same way you deployed them to one Docker server. Note that if you are using custom deployment templates — they have to be updated to support Swarm.<br>The support also extends to the setup recipes mentioned above. Of course, the recipes do need to support Swarm themselves to work correctly.</p><p>I would love to hear your feedback on this new release. Feel free to send it over to <a href="https://github.com/exoframejs/exoframe/issues">GitHub</a> or <a href="https://twitter.com/yamalight">Twitter</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8ab6f4e05b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/announcing-exoframe-3-0-easy-complex-deployments-docker-swarm-support-c8ab6f4e05b2">Announcing Exoframe 3.0 — easy complex deployments &amp; Docker Swarm support</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Exoframe 2.0 — deploy anything within minutes]]></title>
            <link>https://medium.com/hackernoon/announcing-exoframe-2-0-deploy-anything-within-minutes-264fdcc4d6?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/264fdcc4d6</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 13:47:31 GMT</pubDate>
            <atom:updated>2018-01-24T13:47:31.553Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<blockquote>Exoframe is a self-hosted tool that allows simple one-command deployments using Docker. <br>If you are not familiar with it — you can find out more in the <a href="https://hackernoon.com/announcing-exoframe-1-0-simple-docker-deployment-tool-59bde252139d">article on initial release</a> and the <a href="https://github.com/exoframejs/exoframe">project repository</a>.</blockquote><p>I am happy to announce the release of <a href="https://github.com/exoframejs/exoframe">Exoframe</a> 2.0!<br>This release includes a number of additions requested by the community as well as migration of Exoframe server to <a href="https://github.com/fastify/fastify">Fastify</a> and tests to <a href="https://facebook.github.io/jest/">Jest</a>.</p><h3>Project templates</h3><p>The major highlight of 2.0 release is the support for 3rd party templates.<br>With this, Exoframe is no longer limited to deploying Node.js, static HTML, Docker and docker-compose projects. It is now possible to deploy any kind of projects — as long as you have a right template installed!<br>Templates will either auto-detect the type of project you are deploying or can be explicitly set through Exoframe config file.</p><p>Along with the support for templates, I’m releasing three basic templates for <a href="https://github.com/exoframejs/exoframe-template-maven">Maven</a>, <a href="https://github.com/exoframejs/exoframe-template-java">Java</a> and <a href="https://github.com/exoframejs/exoframe-template-tomcat">Tomcat</a> projects.</p><p>You can read more about templates in <a href="https://github.com/exoframejs/exoframe/tree/master/docs">the docs</a>.<br>If you are interested in creating your own template — have a look at <a href="https://github.com/exoframejs/exoframe/blob/master/docs/TemplatesGuide.md">this guide</a>.</p><h3>Traefik 1.5 with Letsencrypt challenge fix</h3><p>Another major change is update to <a href="https://blog.containo.us/traefik-1-5-cancoillotte-is-here-7bd6713ae135">Traefik 1.5.0</a> that has added support for ACME HTTP challenge which is required for letsencrypt to work correctly since TLS-SNI-0x challenge was disabled.</p><h3>More goodies</h3><p>Other smaller (but awesome) additions include:</p><ul><li>You can now set <a href="https://github.com/exoframejs/exoframe/blob/master/docs/Basics.md#project-config-file">additional container labels</a> via Exoframe config (useful when you want to e.g. pass additional Traefik parameters)</li><li>Server can now has optional <a href="https://github.com/exoframejs/exoframe-server#configuration">CORS support</a> that can be enabled via config</li><li>It is now possible to <a href="https://github.com/exoframejs/exoframe-server#configuration">configure Traefik instance</a> used with Exoframe server (e.g. you can use it with your own Traefik instance)</li><li>For those of you willing to try out the latest versions — there is now <a href="https://github.com/exoframejs/exoframe/blob/master/docs/Nightly.md">a way to update to nightly builds</a> for both server and CLI</li></ul><p>I would love to hear your feedback on this new release. Feel free to send it over to <a href="https://github.com/exoframejs/exoframe/issues">GitHub</a> or <a href="https://twitter.com/yamalight">Twitter</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=264fdcc4d6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/announcing-exoframe-2-0-deploy-anything-within-minutes-264fdcc4d6">Announcing Exoframe 2.0 — deploy anything within minutes</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Exoframe 1.0 — simple Docker deployment tool]]></title>
            <link>https://medium.com/hackernoon/announcing-exoframe-1-0-simple-docker-deployment-tool-59bde252139d?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/59bde252139d</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Mon, 23 Oct 2017 13:05:44 GMT</pubDate>
            <atom:updated>2017-10-23T13:05:44.371Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><a href="https://github.com/exoframejs/exoframe">Exoframe</a> started with one goal — to provide a simple self-hosted solution that allows one-command deployments using Docker.<br>I’ve been working on Exoframe since its beta announcement about 6 months ago. All that time Exoframe has been used for my personal project as well as for the number of projects we develop in <a href="https://twitter.com/DiceResearch">our research group</a>.</p><p>Today, I am excited to announce the 1.0 release of the Exoframe, a major step for the project. Exoframe is now considered “production ready”.</p><h3>What’s new in 1.0</h3><p>Over the time Exoframe gained a significant number of features that will help you manage and deploy your projects on your servers with ease.<br>Here’s a list of the features that Exoframe 1.0 provides out-of-the-box:</p><ul><li>One-command project deployment</li><li>SSH key based auth</li><li>Rolling updates</li><li>Deploy tokens (e.g. to deploy from CI)</li><li>Automated HTTPS setup via letsencrypt *</li><li>Automated gzip compression *</li><li>Simple access to the logs of deployments</li><li>Docker-compose support</li><li>Multiple deployment endpoints and multi-user support</li><li>Simple update procedure for client, server, and Traefik</li><li>Optional automatic subdomain assignment (i.e. every deployment gets its own subdomain)</li></ul><p>* Feature provided by <a href="https://traefik.io/">Traefik</a></p><h3>What’s next?</h3><p>This release is only the beginning. We’re planning to add a number of exciting and awesome features in the next months. I’ll highlight two of them here:</p><ol><li>We’re planning to add Docker Swarm support that’ll allow you to deploy and scale your projects across multiple servers.</li><li>We’re also going to add support for deployment recipes. Imagine deploying something large and complex (e.g. Apache Spark stack) in one command — this is our goal here.</li></ol><p>And, of course, if you have any suggestions — I’d be happy to <a href="https://github.com/exoframejs/exoframe/issues">hear them</a>!</p><h3>Project links</h3><p>You can get <a href="https://github.com/exoframejs/exoframe">Exoframe on GitHub</a>, it only takes a few minutes to setup.<br>You can check out short <a href="https://www.youtube.com/watch?v=AEwLt5hmKYo">video demo</a> that walks you through setup and usage in ~8 minutes on YouTube.<br>Rest of the useful links along with documentation can be found in <a href="https://github.com/exoframejs/exoframe/tree/master/docs">GitHub repository</a>.</p><p>As usual — any <a href="https://twitter.com/yamalight">feedback is appreciated</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59bde252139d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/announcing-exoframe-1-0-simple-docker-deployment-tool-59bde252139d">Announcing Exoframe 1.0 — simple Docker deployment tool</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Building X with javascript” — help me pick next topic]]></title>
            <link>https://medium.com/@yamalight/building-x-with-javascript-help-me-pick-next-topic-16e6fe53ed02?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/16e6fe53ed02</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 12:42:25 GMT</pubDate>
            <atom:updated>2017-09-06T12:42:25.466Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Hi, I’m Tim and I’m doing free open source courses on building things with javascript. So far I’ve done a course on <a href="https://github.com/yamalight/building-products-with-js">building client-server products</a> and <a href="https://github.com/yamalight/bpjs-electron">desktop applications</a>.<br>Now is time to pick a topic for the next course — and I need your help!<br>As usual, the course will be published on <a href="http://github.com/yamalight/">GitHub</a> and <a href="https://www.youtube.com/channel/UCPkKhlR0sXtN5hlB228xuTg">YouTube</a>, with livestreams happening on <a href="https://www.twitch.tv/yamalight">Twitch</a>.</p><p>If you prefer video format, you can watch the video below. Otherwise — read on!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDkSssXq9MrI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDkSssXq9MrI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDkSssXq9MrI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/14bfc752aadb3b45922b0173b4041ca2/href">https://medium.com/media/14bfc752aadb3b45922b0173b4041ca2/href</a></iframe><p>I’ve prepared 5 topics for you to pick from.<br>Those are:</p><p><strong>1. Data science/analytics project</strong></p><p>This is what I do during my day-to-day work, so I can offer the most in-depth course on this topic.<br>I’m planning to cover data scraping, cleaning, processing, and visualization, along with microservice-based data processing pipelines.</p><p>Since this is an area I’m quite familiar with, I’d already come up with a good project — we’re going to process product reviews and present them in a more meaningful way than arbitrary stars or numbers.</p><p><strong>2. Embedded programming with Raspberry-Pi</strong></p><p>We’re going to build a RPi-based thing. My best idea was to build a small homebrew gaming console.<br>I’m planning to cover basics of embedded programming, working in environments with limited resource and specifically — working with RPi.</p><p><strong>3. Bots</strong></p><p>We’re going to build a simple bot. No ideas here, so I’m open to suggestions :)<br>I’m planning to cover basic bot building and usage of third-party bot API (discord, twitch, etc) in a unified way.</p><p><strong>4. Mobile app using React-Native</strong></p><p>We’re going to build a mobile application using React-Native. Best idea so far was to build an Instagram clone — any better ideas are welcome!<br>I’m planning to cover basic mobile development (which is required to work with RN) and, of course, using React-Native itself.</p><p><strong>5. Applied Machine Learning</strong></p><p>We’re going to build a system that’d utilize Machine learning is some way. Best idea I had so far is actually to add that to the topic (1) since it fits quite well.<br>I’m planning to cover primarily usage of ML as a developer.</p><h3>I want to learn!</h3><p>If you are interested in any of those topic and/or have a good idea for projects, please fill out <a href="https://goo.gl/forms/04vlSWdec6GILFS82">this survey</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16e6fe53ed02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous deployment for your Node.js projects in 10 minutes with Exoframe]]></title>
            <link>https://medium.com/hackernoon/continuous-deployment-for-your-node-js-projects-in-10-minutes-with-exoframe-bdf48340c1be?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdf48340c1be</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Wed, 23 Aug 2017 14:31:27 GMT</pubDate>
            <atom:updated>2017-08-23T14:31:27.016Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Setting up continuous deployment for your project can be quite tricky. Puppet, Ansible, Chef — all those tools are great, but sometimes you just want something small and simple to use to deploy your pet projects to your virtual or dedicated server.<br>I want to show you how to setup continuous deployment for your Node.js project with rolling updates, HTTPS and all that fancy stuff in ~10 minutes using <a href="https://github.com/exoframejs/exoframe">Exoframe</a>.</p><p>For demo purposes we’re going to be deploying simple Node.js project based on Express.js, you can find the source code (along with all the other mentioned bits) in this GitHub repo: <a href="https://github.com/exoframejs/node-cd-demo">https://github.com/exoframejs/node-cd-demo</a></p><p>If you prefer video format to reading, you can watch me doing the whole walkthrough here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAEwLt5hmKYo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAEwLt5hmKYo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAEwLt5hmKYo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a411ed510b444b88e80ff2e86376f400/href">https://medium.com/media/a411ed510b444b88e80ff2e86376f400/href</a></iframe><h3>Preparing the server</h3><p>Before you get started, you obviously need a server. If you already have one — awesome. If not, grab one at <a href="https://www.hetzner.com/?country=ot">Hetzner</a> / <a href="https://www.digitalocean.com/">DO</a> / <a href="https://www.vultr.com/">Vultr</a> or whatever hoster you prefer.</p><p>Once you’d setup the server with your favorite OS, you will need to <a href="https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server">configure public key SSH authentication</a>. <br>This is required because Exoframe uses private-public key pairs for authentication process. <br>If you are using login-password pairs for SSH authentication, I strongly recommend switching to <a href="https://security.stackexchange.com/questions/69407/why-is-using-an-ssh-key-more-secure-than-using-passwords">public-private key method</a>.<br>Also note the part in the linked article about disabling password authentication after you are done with public key authentication part— that is also a must-have, in my opinion.</p><p>Once you are done with that — you’ll need to <a href="https://docs.docker.com/engine/installation/">install Docker</a> since Exoframe relies on it for service execution and management.<br>After you’ve finished with docker, all you need to start <a href="https://github.com/exoframejs/exoframe-server">Exoframe server</a> is to execute the following command:</p><pre>docker run -d \<br>  -v /var/run/docker.sock:/var/run/docker.sock \<br>  -v /path/to/exoframe-folder:/root/.exoframe \<br>  -v /home/user/.ssh/authorized_keys:/root/.ssh/authorized_keys:ro \<br>  -e EXO_PRIVATE_KEY=your_private_key \<br>  --label traefik.backend=exoframe-server \<br>  --label traefik.frontend.rule=Host:exoframe.your-host.com \<br>  --name exoframe-server \<br>  exoframe/server</pre><p>Be sure to change the parameters to fit your server — you want to at least:</p><ol><li>Set EXO_PRIVATE_KEY to something unique. It’s used during generation of authentication tokens.</li><li>Set --label traefik.frontend.rule=Host:exoframe.your-host.com to point to your host. It’s used to expose Exoframe server API endpoint.</li></ol><p><em>Important note</em>: This will also start an instance of <a href="https://traefik.io/">Traefik</a> that will occupy ports 80 and 443. It is used to route requests to your deployed services, setup HTTPS, etc.</p><p>For more detailed explanation of those parameters and startup procedure, see <a href="https://github.com/exoframejs/exoframe-server#installation-and-usage">docs in Exoframe server GitHub repository</a>.</p><h3>Testing deployment from CLI</h3><p>Before configuring continuous deployment, we need to make sure that Exoframe server works fine.<br>To do that, we’re going to install Exoframe CLI locally and deploy our project manually to see if that works.<br>Currently, Exoframe CLI only works on Node 8+ because it relies on async/await, so make sure you have the latest Node installed.<br>To install Exoframe CLI locally simply execute:</p><pre>npm install exoframe -g</pre><p>Now that we have it installed, we need to point it to our new server. You can do that by executing the following command:</p><pre>exoframe endpoint http://you.server.url</pre><p>Once finished, you will need to login into your server by running the following command and selecting the private key that is used for authentication with your server (and possibly entering passphrase for your private key):</p><pre>exoframe login</pre><p>After you have successfully logged in, you can deploy your project. But before deployment, we’ll do one last thing — generate a new project configuration file. This can be done by executing the following command inside of the project folder:</p><pre>exoframe config</pre><p>The command will guide you through the config creation in interactive manner. For this demo, the only important field there would be “domain”.</p><p><em>Important note</em>: since Exoframe doesn’t know what is entry point of your Node.js project, it’ll simply execute npm start on deployment and expect service to listen on port 80. So, make sure that you have start script in your package.json and use port 80!</p><p>Once desired domain for your new deployment has been set, you can deploy the project by simply running this command inside of the project folder:</p><pre>exoframe</pre><p>After Exoframe CLI reports that project has been deployed, you should test its availability on the domain you have entered during config step.<br>If everything works as expected — we’re green to setup continuous delivery!</p><h3>Configuring continuous delivery with Travis-CI</h3><p>We’re going to use Travis-CI for testing and deploying our project.<br>Here’s a simple .travis.yml config for Node.js project:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/413160ffc6e63d6ef1c7b2247a906fe2/href">https://medium.com/media/413160ffc6e63d6ef1c7b2247a906fe2/href</a></iframe><p>Travis does most of the work on testing Node.js projects for us, so all we need to care about here is specifying language and Node.js version. You can read more about that in <a href="https://docs.travis-ci.com/user/languages/javascript-with-nodejs/">official Travis-CI docs</a>.</p><p>Now that we have Travis config file and we’ve made sure it works, we need to add Exoframe deployment to it.<br>Exoframe has a special feature called “deployment tokens” that allows you to deploy projects to your server without the need to login using your private key. So, to setup the deployment, we first need to generate such token. This can be easily done by executing the following command:</p><pre>exoframe token</pre><p>Upon execution you should get a freshly generated token that can be used to deploy projects to current Exoframe server.</p><p><em>Important note</em>: Make sure to save the token as there’s no way to read it again, only to generate a new one.</p><p>Once you have the token, you want to use <a href="https://docs.travis-ci.com/user/encryption-keys/">Travis-CI encryption system</a> to store encrypted token in your Travis config, like so:</p><pre>travis encrypt EXO_TOKEN=&quot;your-token-here&quot;</pre><p>After that, you’ll need to tweak the config itself to install Exoframe CLI before running tests and to trigger deployment after tests has been successful. <br>Config file should look something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e590ed892631a7e68c985878b31e9059/href">https://medium.com/media/e590ed892631a7e68c985878b31e9059/href</a></iframe><p>After you’ve push it to GitHub, you should be able to open Travis logs and watch your project being deploy to your server.</p><h4>Bonus: Rolling updates</h4><p>Note the tiny -u flag in the config above. That tells Exoframe server to execute a rolling update for the current deployment.<br>The way it works is pretty simple — it’ll deploy new version, wait for it to start and then tear down the old one, which will result in zero downtime deployments.</p><h4>Bonus: Other project types</h4><p>Exoframe also supports other project types!<br>Currently, along with Node.js project, you can also deploy static HTML projects, Docker project and Docker-Compose projects.</p><h3>Give it a try!</h3><p>If you found Exoframe interesting — give it a shot!<br>It is <a href="https://github.com/exoframejs/exoframe">available right now on GitHub</a>.<br>As usual — any feedback as well as contributions are appreciated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdf48340c1be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/continuous-deployment-for-your-node-js-projects-in-10-minutes-with-exoframe-bdf48340c1be">Continuous deployment for your Node.js projects in 10 minutes with Exoframe</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Exoframe (beta) — self-hosted alternative to Now.sh]]></title>
            <link>https://medium.com/hackernoon/introducing-exoframe-beta-self-hosted-alternative-to-now-sh-80643f96b84b?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/80643f96b84b</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Mon, 17 Jul 2017 19:04:31 GMT</pubDate>
            <atom:updated>2017-07-17T19:08:45.309Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Back in September 2016 I’ve <a href="https://hackernoon.com/simplifying-docker-management-with-exoframe-9275e92c7406">presented</a> the first public version of Exoframe. At a time I’ve positioned it as a tool to simplify management of Docker. The idea was pretty simple — take away the pain of writing, maintaining and deploying docker images to your server. <br>That was done through templates and project detection — Exoframe alpha would read your project directory, try to figure out which template to use, add Dockerfile from that template and then deploy it to your server while asking you a bunch of questions.<br>In a long run — it didn’t quite work out for me (or anyone else according to download statistics). It was annoying to answer so many questions on each deploy, there was no way to easily assign domains to demos and most of the Docker features that I’d coded into deploy step were not used as frequently as I thought they would. So, at some point I just stopped using it altogether.</p><p>Then I discovered <a href="http://now.sh/">Now.sh</a> from <a href="https://zeit.co/about">ZEIT</a>. It’s an amazingly simple tool that allows you to deploy Node, HTML and Docker projects in one command. No questions asked.<br>Even though Now is great and gets even better with every update (e.g. <a href="https://zeit.co/blog/universal-now">latest update</a> allows you to work with GCP, AWS and Azure), it still has it’s limitations. Biggest one for me is the fact that I cannot use it with my own servers. I’m sure some of you also have a few demo servers at work, one or two VPSes you already own and maybe even some dedicated servers just for fun. Sadly, currently there’s no way to run self-hosted Now.<br>Another issue is complex docker projects — while Now allows you to deploy project from simple Dockerfile, there’s now way to deploy one using <a href="https://docs.docker.com/compose/">docker-compose</a> that describes multiple services (e.g. database with backend and front-end).</p><p>That’s why I decided to re-think and re-build Exoframe to address all those issues. Think of it as a self-hosted alternative to Now that allows you to easily deploy your projects to your server, while getting automated domain configuration, load balancing, HTTPS (thanks to letsencrypt) and all that good stuff.</p><p>If you prefer video format, you can watch the demo and explanation of how it works in the video below. If you prefer text — scroll on :)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVZnYKIoh5oA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVZnYKIoh5oA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVZnYKIoh5oA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c1dd0e4898c794f0b4da0b4f0ed95642/href">https://medium.com/media/c1dd0e4898c794f0b4da0b4f0ed95642/href</a></iframe><h3>Exoframe server and how it works</h3><p>The way Exoframe works is pretty straightforward — the only thing you will need to install it is a server with <a href="https://docs.docker.com/engine/installation/">Docker daemon</a>. Some server providers even have pre-configured servers (e.g. <a href="https://www.digitalocean.com/products/one-click-apps/docker/">one-click Docker server from DigitalOcean</a>).</p><p>Exoframe server itself works in a pretty simple way — upon execution, it’ll spawn an instance of <a href="https://traefik.io/">Traefik</a> that’ll handle domain management, HTTPS, load balancing and all that stuff.<br>Then it simply gets packaged projects from Exoframe CLI and deploys it to your Docker daemon while configuring Traefik and Docker for you.<br>Authentication is done using private-public RSA keys, so normally you wouldn’t need any additional setup if you already can SSH into your server using your private key. If you are still using login and password for SSH, see <a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-ssh-keys--2">this guide</a> that’ll help you to switch to more secure key authentication.</p><p>All you need to do to set the whole thing up is to execute Exoframe server within your Docker daemon, like so:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49371df79666a771407a2fcc8d9687e5/href">https://medium.com/media/49371df79666a771407a2fcc8d9687e5/href</a></iframe><p>This command will start Exoframe server, allow it to access your docker via <em>docker.sock</em>, link config folder to your local folder to persist configuration upon restarts/updates/etc, link your <em>authorized_keys</em> files for authentication and finally — setup rules for <a href="https://traefik.io/">Traefik</a>. You can find more detailed explanation of each line in the <a href="https://github.com/exoframejs/exoframe-server">server repository</a>.</p><h3>Exoframe client and commands</h3><p>Once Exoframe server is up, you’ll want to install Exoframe CLI. Currently, this can only be done using npm, so you’ll need latest <a href="https://nodejs.org/en/download/package-manager/">Node.js and npm installed on your system</a>.<br>Once you have them, you can install exoframe using the following command:</p><pre>npm install exoframe -g</pre><p>After that you will need to point Exoframe CLI to your newly set up server using the following command:</p><pre>exoframe endpoint http://exoframe.server.url</pre><p>And finally login into it by using exoframe login and selecting the private key that has been authorized to access your server.</p><p>Once logged in, you’ll get access to main commands:</p><ul><li>exoframe [deploy] — deploys current project to your server</li><li>exoframe config — generate new config file for current project</li><li>exoframe list | ls — lists active deployments</li><li>exoframe remove | rm &lt;id&gt;— removes active deployment</li><li>exoframe logs | log &lt;id&gt; — displays logs for active deployment</li></ul><p>The deploy command currently understands and is able to handle the following project types:</p><ol><li>Static HTML based projects — will be deployed using <a href="http://hub.docker.com/_/nginx">nginx</a> image</li><li>Node.js based projects — will be deployed using <a href="https://hub.docker.com/_/node">node:alpine</a> image</li><li>Docker based projects— will be deployed using your <a href="https://docs.docker.com/engine/reference/builder/">Dockerfile</a></li><li>Docker-compose based projects— will be deployed using your <a href="https://docs.docker.com/compose/compose-file/">docker-compose</a> file</li></ol><p>Configuration for deploy command is done using config file that contains the name of your project, domain you want to assign to it, environment you want to set, restart policy and internal container hostname. Structure of config file is <a href="https://github.com/exoframejs/exoframe#project-config-file">covered in Exoframe readme</a>.</p><h4>HTTPS with letsencrypt</h4><p>Since Exoframe uses Traefik to manage domains, you get out-of-the-box support for HTTPS with letsencrypt certificates!<br>To enable it, you’ll need to edit your server config file and set the following fields:</p><pre>letsencrypt: true # whether to enable letsencrypt, default &quot;false&quot;<br>letsencryptEmail: your@email.com # email used for letsencrypt</pre><p>Once this has been set, just start your Exoframe server.<br><strong>Warning:</strong> If you already had Exoframe server and Traefik running, you’ll also need to remove old Traefik instance from Docker daemon and restart Exoframe server. This is required since Traefik needs to be re-created with additional letsencrypt parameters.<br>Once this is done — all your projects will be automatically deployed to HTTPS with letsencrypt certificates!</p><h4>Automatic subdomain generation</h4><p>Exoframe server also allows you to enable automatic subdomain names generation (similar to how Now.sh does it, but with your domain). This can be done by setting baseDomain field in server to config to the top domain you want to use. E.g. setting it to .codezen.net will result in deployed services without explicitly specified domain names getting domains like exo-user-demo-d234ah3.codezen.net <br>This is useful when you want to quickly deploy and test your projects without using the real domain name for them.</p><h3>Current limitations</h3><p>Exoframe obviously has its own limitations:</p><ul><li>Largest one being limited support for docker-compose projects configuration. While Exoframe can easily manipulate containers it deploys directly, changing configuration of docker-compose services is quite limited. Because of that, you’ll have to set e.g. <a href="https://docs.traefik.io/basics/#frontends">Traefik labels</a> for domains manually. Unfortunately, there’s no real way to “fix” this issue but to provide better docs.</li><li>Another limitation is the fact that currently you can only login using private-public key pairs. While this works pretty well for people, using it from CI/CD daemon is not exactly nice. I am planning to address that in future by adding deploy tokens that’d allow re-deploying one specific project without need to authenticate using private key.</li><li>One more obvious limitation is support for only 4 project types. While Dockerfile and Docker-compose projects do allow users to deploy pretty much anything, it could be nice to have more autoconfigured projects. I am planning to address this in future by introducing plugin system to project deployments if there’s enough interest in it.</li></ul><h3>Conclusions</h3><p>If you found Exoframe interesting — give it a shot!<br>The beta is <a href="https://github.com/exoframejs/exoframe">available now on GitHub</a>.<br>As usual — any feedback as well as contributions are appreciated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80643f96b84b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/introducing-exoframe-beta-self-hosted-alternative-to-now-sh-80643f96b84b">Introducing Exoframe (beta) — self-hosted alternative to Now.sh</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making a free open source CC/MIT licensed course on building products using javascript]]></title>
            <link>https://medium.com/hackernoon/making-a-free-open-source-cc-mit-licensed-course-on-building-products-using-javascript-d43cd6442d62?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d43cd6442d62</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[teaching]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 19:14:38 GMT</pubDate>
            <atom:updated>2017-07-17T17:00:16.702Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Hi, my name’s Tim and you might remember me from <a href="https://hackernoon.com/i-want-to-teach-you-to-build-products-using-javascript-for-free-8900dc836961#.3tdrc7919">my original post</a> I made about 8 months ago — I promised to teach people to build products using javascript for free. No strings attached. <br>The idea was to make a course that showcases and talks about technologies that are used day-to-day in development (intermediate/advanced level), not talk about development basics.<br>Few days ago I’ve uploaded the final video of the course. All materials are published absolutely free, without any ads and under permissive licenses (MIT for code, Creative Commons for videos).</p><p>The course ended up containing <a href="https://www.youtube.com/playlist?list=PL_gX69xPLi-ljVdNhspjZUlPmBNjRgD2X">11 core videos</a> (along with a bunch of off-topic videos on related topics) that go through the process of creating the client-server application using javascript. Node.js along with libraries like express.js, passport, etc is used on a backend. React with Webpack, Redux, RxJS and that kind of stuff is used on front-end. All of that is packaged into Docker containers, tested and deployed using Gitlab-CI.<br>The videos cover the full process of creating the app:</p><ul><li>figuring out the idea,</li><li>setting up a project with git,</li><li>picking a database,</li><li>using docker for development and deployment,</li><li>building REST API,</li><li>building web app client for that API with React/webpack/etc,</li><li>unit testing all that,</li><li>and finally — (continuously) deploying it with Docker and Gitlab-CI.</li></ul><p>Additionally, per request of the viewers, I have livestreamed the process of development that preceded most of the published videos. <br>I’ve ended up doing <a href="https://www.youtube.com/playlist?list=PL_gX69xPLi-nM52i7LyeEo8Rpu9t_s9tV">13 livestreams</a> that cover most of the video content I did. Most of them are quite lengthy and are not required to understand the course, but might contain some additional information (along with my poor habits of copy-pasting things)</p><p>I’m writing this post for two main reasons:</p><ol><li>Maybe there are some people who’ll find the course interesting and this post will help them discover it</li><li>I need your help to decide what to cover next!</li></ol><p>Doing this course was quite a lot of fun. I had to learn a ton of things myself and received a lot of very interesting feedback, suggestions and questions from the viewers. So I want to keep doing that.</p><p>And now I need your help to figure out what area to talk about in the next series. Here are some of the topics I personally think would be cool to do and talk about:</p><ul><li>General introduction to web technologies (in-depth introduction to web technologies that prepares you for the published course)</li><li>Creating mobile apps using web technologies</li><li>Creating desktop apps using web technologies</li><li>Building real-time apps using WebSockets</li><li>Adding features (e.g. offline, push notifications) using Service Workers</li><li>Applying Machine Learning for fun and profit</li><li>Using WebAssembly (hot off the press, would be fun to play with)</li></ul><p>If any of those sound interesting and you want to help me figure out what to do next — please leave a response to <a href="https://www.youtube.com/watch?v=okVXyUZHKbU&amp;feature=youtu.be">my conclusions video</a>.<br>And, of course, I’ll be happy to answer any questions you might have!</p><p>Some links to the related resources:</p><ul><li><a href="https://github.com/yamalight/building-products-with-js">Project source code</a></li><li><a href="https://www.youtube.com/playlist?list=PL_gX69xPLi-ljVdNhspjZUlPmBNjRgD2X">Course videos playlist</a></li><li><a href="https://www.youtube.com/playlist?list=PL_gX69xPLi-nM52i7LyeEo8Rpu9t_s9tV">Livestream videos playlist</a></li><li><a href="https://www.reddit.com/r/BuildingWithJS/">Course subreddit</a></li><li><a href="https://discord.gg/hnKCXqQ">Course Discord chat</a> (I’m always happy to answer questions and help you!)</li><li><a href="https://www.facebook.com/buildingproductswithjs/">Facebook page with updates</a></li><li><a href="https://twitter.com/yamalight">My twitter with updates</a> (and other bonkers)</li></ul><p>Cheers,<br>Tim</p><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a>family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>To learn more, <a href="https://goo.gl/4ofytp">read our about page</a>, <a href="http://bit.ly/HackernoonFB">like/message us on Facebook</a>, or simply, <a href="https://goo.gl/k7XYbx">tweet/DM @HackerNoon.</a></blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d43cd6442d62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/making-a-free-open-source-cc-mit-licensed-course-on-building-products-using-javascript-d43cd6442d62">Making a free open source CC/MIT licensed course on building products using javascript</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplifying Docker management with Exoframe]]></title>
            <link>https://medium.com/hackernoon/simplifying-docker-management-with-exoframe-9275e92c7406?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9275e92c7406</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Thu, 08 Sep 2016 15:32:41 GMT</pubDate>
            <atom:updated>2017-08-02T16:55:31.891Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Docker is an <a href="https://medium.freecodecamp.com/a-beginner-friendly-introduction-to-containers-vms-and-docker-79a9e3e119b#.111rlevmh">amazing</a> tool. It can help you <a href="https://medium.com/@RemindEng/introducing-empire-a-self-hosted-paas-built-on-docker-amazon-ecs-7f8beb7f6ae4">setup self-hosted PaaS</a>, <a href="https://medium.com/@andrewmclagan/you-thought-laravel-homestead-was-easy-say-hello-to-docker-2c0639a0501#.z53ssycbo">scale things</a>, do <a href="https://medium.com/@Malinskiy/android-ci-with-docker-a2f522086640">Android CI</a> and even <a href="https://medium.com/google-cloud/developing-for-arduino-with-docker-and-johnny-five-on-osx-cc6813ae6e9d#.k6xwqu87h">develop for IoT</a>.<br>But even though Docker is a great tool, it has its own problems.</p><p>First of all — it’s not that easy to use. Mainly because there are so many different flags you can use during pretty much every step. Even after using it daily for the past few years, I still have to open the manual to remember how to correctly forward ports or how to set resource constraints.</p><p>Then there’s a challenge of setting up an authentication, access control as well as ownership of the images and running containers. Right now you <a href="https://docs.docker.com/engine/extend/plugins_authorization/">can setup authorization</a> using Docker plugins, but it’s far from simple. And it doesn’t give you a way to define ownership. You can, of course, use labels or security opts to set the user. But you’d have to do that manually.</p><p>And that’s if you know how to use Docker. <br>In <a href="http://aksw.org/">our research group</a>, we recently decided to migrate all our demos and services to Docker. Turns out it’s quite hard to teach people what Docker is and how to properly use it. And it’s even harder to make everyone set correct labels and security opts to make sure admins know e.g. who is responsible for container causing trouble.</p><p>And so I set out to create a better, simpler way of working with Docker.</p><p><strong>Update:</strong> <a href="https://hackernoon.com/introducing-exoframe-beta-self-hosted-alternative-to-now-sh-80643f96b84b">Exoframe beta is out</a>! Simpler, faster, smaller and as user-friendly as ever.</p><h3>Meet Exoframe —a power armor for docker containers</h3><p>The idea behind Exoframe is quite simple — to help users tackle the aforementioned problems in a simple intuitive way with as little configuration as possible. <br>Sort of, to give you a way to use it as a power armor to move those heavy docker containers around.</p><p>Exoframe consists of two parts: <a href="https://github.com/exoframejs/exoframe-server">Exoframe server</a> and <a href="https://github.com/exoframejs/exoframe">Exoframe CLI</a>.</p><p>Exoframe server is installed alongside your Docker on the remote server you want to use for deployment. It is essentially as a smart proxy for <a href="https://docs.docker.com/engine/reference/api/docker_remote_api/">Docker remote API</a> with authentication, access control and ownership features.</p><p>Exoframe CLI is installed on your local machine and is used for all the common Docker tasks like building and deploying images using Exoframe server API.</p><h4>Exoframe server setup</h4><p>First, you will need to setup Exoframe server.<br>Since your server should already be running docker, it’s quite easy to do:</p><pre>docker run -d \<br>  -p 3000:3000 \<br>  -v /var/run/docker.sock:/var/run/docker.sock:ro \<br>  -v /path/to/exoframe-folder:/root/.exoframe \<br>  exoframe/server</pre><p>This will start an Exoframe server, forward port 3000 to your host and init default Exoframe server config. <br>Be sure to navigate to <em>/path/to/exoframe-folder</em> and adjust username and password in <em>server.config.yml </em>because default admin:admin pair is not exactly secure :)<br>You can also configure additional server auth plugins (e.g. LDAP or your other corporate user DB) that can be used instead of config-based user list.</p><p>Done. The server is ready to work!</p><h4>Exoframe CLI setup</h4><p>Next, you will need to setup Exoframe CLI on your local machine.<br>Since Exoframe is written using Node.js, you will need to have Node.js (v6 or later) <a href="https://nodejs.org/en/download/package-manager/">installed</a>. Once you have it, simply execute npm install command to get Exoframe CLI:</p><pre>npm install exoframe -g</pre><p>Once install finishes, you can specify your server endpoint using the following command:</p><pre>exoframe endpoint <a href="http://you.server.url/">http://your.server.url</a>:3000</pre><p>Then execute “<em>exoframe login</em>” to authenticate on the server and you are ready to go!</p><h4>Building and deploying an example project</h4><p>Now let’s see it in action! <br>We are going to create, build and deploy a simple static HTML project.<br>You can find all the steps explained below in one simple screencast on asciinema:</p><p><a href="https://asciinema.org/a/85154">Exoframe short demo</a></p><p>First, create a new folder and add a new index.html file that has some content, e.g.:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0f39682cb28dc209c82a785691b51e9e/href">https://medium.com/media/0f39682cb28dc209c82a785691b51e9e/href</a></iframe><p>Then, execute “<em>exoframe build</em>” and pick a name for your image (or just leave it as a default one):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*0lxGo4QJifRi_WUqW0NQOw.png" /><figcaption>Exoframe build command output</figcaption></figure><p>At this point, Exoframe will automatically detect the project type and pick a suitable Dockerfile for it. Since we only have one <em>index.html </em>file, Exoframe reasons that it might be suitable for basic Nginx image.<br>This detection is done using the templating engine. Templates are simple Node.js packages that provide a set of methods to detect if a project is suitable for them, ignore files, add type-specific labels and ask a user for additional input if required. The output of the template is a complete Dockerfile that is used to build a project.<br>You can find an example of Nginx template that is used in this case <a href="https://github.com/exoframejs/exoframe-template-nginx">on GitHub</a>.</p><p>Once the build is finished, you can get list of your owned images and services using “<em>exoframe list</em>” command:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*2HGJLiC4Kxv8aH_MEKC_cQ.png" /><figcaption>Exoframe list command output</figcaption></figure><p>Now that you have built a new image, let’s deploy it.<br>Simply execute “<em>exoframe deploy</em>” and you will get a list of available images to deploy — no need to remember all of your image names:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*DDVJuwQdruQ3LhpAH_VSqQ.png" /><figcaption>Exoframe deploy images selection</figcaption></figure><p>Once you’ve selected the image you want to deploy, Exoframe will ask what exactly do you want to do during the deployment — do your want to forward ports, specify restart policy, etc?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*BBAlekQsnsBTGZUYRefGzA.png" /><figcaption>Exoframe deploy feature selection</figcaption></figure><p>In this case we only want to forward ports, so that’s what is selected in the screenshot above. After you hit enter, Exoframe will present you with additional inputs that will guide you through all of the selected actions, e.g. for ports input looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*I97GWrvETepBygbpA3GW7w.png" /><figcaption>Exoframe deploy port mapping example</figcaption></figure><p>Note that Exoframe shows you inline how the port mappings should look and which of the ports is inside a container and on a host. As you can see, it also allows you to map multiple ports.</p><p>After hitting enter, you will see a message that says the image was successfully deployed. You can now see your new service in a list that we have already called before using “<em>exoframe list</em>”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*ah3hwoRVvzLVJ-A7Yv6NQw.png" /><figcaption>Exoframe list with full info about running service</figcaption></figure><p>As you can see, the list now includes running <em>html-test</em> service with full info about it — forwarded ports, status, template, name.<br>If you open your browser at <a href="http://your.domain/">http://your.domain</a> you should see the static HTML you’d created.</p><p>Now that you’ve seen that service works, let’s stop and remove it.<br>You can use “<em>exoframe stop</em>” command to stop your running services and “<em>exoframe rm</em>” to remove stopped services. Once again, you don’t need to remember names of your services, if you don’t provide service name — Exoframe will present you with an interactive list:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*oonwR9KUUI4aQPZpdY3gvw.png" /><figcaption>Exoframe stop command example</figcaption></figure><p>Exoframe also provides a way to interact with images from registries.<br>Using “<em>exoframe pull &lt;image&gt;</em>” will pull given image from docker registry.<br>You can then get list of all locally available registry images by executing “<em>exoframe list public</em>” command:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*AU45uAH4K0vfCYiq_HojZA.png" /><figcaption>Exoframe registry images list</figcaption></figure><p>Deployment of the images from registry can be done by executing deploy command with an additional image argument, e.g.:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*uNDlurMLzr0bPTmY8FTNTg.png" /><figcaption>Exoframe deployment of registry image</figcaption></figure><p>After that running services can be managed in the same manner as shown above.</p><h3>Conclusion</h3><p>Exoframe is still in its alpha stage and some features are missing here and there. But I’ve been already using it to manage and deploy a set of demos on my own servers and it made my life a lot easier.</p><p><a href="https://github.com/exoframejs/exoframe">Exoframe is available now on GitHub</a>. Free. Licensed under MIT.<br>Any feedback you might have is highly appreciated.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><a href="https://goo.gl/Ahtev1"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9275e92c7406" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/simplifying-docker-management-with-exoframe-9275e92c7406">Simplifying Docker management with Exoframe</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I want to teach you to build products using javascript. For free.]]></title>
            <link>https://medium.com/hackernoon/i-want-to-teach-you-to-build-products-using-javascript-for-free-8900dc836961?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8900dc836961</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Thu, 14 Jul 2016 17:26:47 GMT</pubDate>
            <atom:updated>2017-07-13T21:47:59.151Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p><strong>Update:</strong> The course is now finished. See <a href="https://medium.com/@yamalight/making-a-free-open-source-cc-mit-licensed-course-on-building-products-using-javascript-d43cd6442d62#.blts7umkn">new post</a> for more details!</p><p>Here’s the thing — there’s a whole lot of different online courses, articles, tutorials and other materials on how to program in javascript (or any other language). And some of those are amazingly good, e.g. <a href="https://github.com/getify/You-Dont-Know-JS">You Don’t Know JS</a>. But none of them actually tell you how to build something real, how to build a product.<br>That’s why I decided to make a simple online course that will try to teach you how to build a complete product — starting from the basic idea and going towards the working application. The focus mostly will not be on programming itself, but rather on high-level concepts, tools and approaches that I am using as a developer in my daily work.</p><p>I’m planning to cover the full lifecycle of the product — starting with the idea, creating new project, using version control, building server, picking database, building web, mobile and desktop apps and configuring continuous deployment. Maybe also some real-time work and machine learning, if there’s interest.<br>I also want it to be more than just a preset list of topics — I am very much open to all questions and suggestions you might have. And if there’s a lot of interest in a specific area — I will make an additional spin-off videos covering those areas.</p><p>All of the content I produce (this includes code, videos, texts, etc) will be released under nonrestrictive licenses and will be available for free with no ads or any other monetization. Feel free to fork, improve and remix any parts of it :)</p><p>Here’s the first video where I talk about the product idea and basic tools you’ll need to follow me:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvkuKW_wuFq4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvkuKW_wuFq4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvkuKW_wuFq4%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d9e200199e88c86c816c91fdd752c6df/href">https://medium.com/media/d9e200199e88c86c816c91fdd752c6df/href</a></iframe><p>If you find the topic interesting — subscribe to the YouTube channel. Even though I might post more related things on Medium, I’m planning to mostly do the course on YouTube.<br>If not — feel free to let me know why, I would love to get any feedback you might have.<br>Thanks! :)</p><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a>family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp;sponsorship</a> opportunities.</blockquote><blockquote>To learn more, <a href="https://goo.gl/4ofytp">read our about page</a>, <a href="http://bit.ly/HackernoonFB">like/message us on Facebook</a>, or simply, <a href="https://goo.gl/k7XYbx">tweet/DM @HackerNoon.</a></blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8900dc836961" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/i-want-to-teach-you-to-build-products-using-javascript-for-free-8900dc836961">I want to teach you to build products using javascript. For free.</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a platform for serverless data-driven applications with Node.js and microservices]]></title>
            <link>https://medium.com/adopting-microservices-architecture/building-a-platform-for-serverless-data-driven-applications-with-node-js-and-microservices-4b543dd7d3ec?source=rss-94ac54b64fc4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b543dd7d3ec</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[scaling-microservices]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Tim Ermilov]]></dc:creator>
            <pubDate>Thu, 24 Mar 2016 10:08:49 GMT</pubDate>
            <atom:updated>2016-06-15T20:02:55.212Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>I would imagine that it’s a dream of every developer — to be able to write pure logic and to be able push it live with a touch of a button. No worries about frameworks, deployment procedures, provisioning, etc — just your business logic. Kind of like magic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*DAmGmpsUjjCxJZaY.jpg" /></figure><p>Of course, I had dreamed about something like this as well.<br>Even though I do enjoy tinkering with docker, checking out new shiny libraries and frameworks (hey, I’m primarily writing javascript after all!) — sometimes I just want to quickly build a solution for a very specific problem.<br>Most likely the problem itself is not even that interesting (or hard) to solve. I just need to solve it within a given time.</p><p>That’s where you’ll start thinking about scaffolding the project. Let’s have a look at how you create a modern project, shall we?<br>For the sake of simplicity, I’ll stick to full stack node.js application here. And I’ll assume we use the latest stable node.js.<br>Once again, for the sake of simplicity we won’t touch on topics like server-side rendering and all that more advanced stuff. It’s gonna be a simple REST API plus a standalone web UI for it.</p><h4>REST API</h4><p>We’ll start with a server-side and a basic REST API. Let’s see what questions you’ll have to answer <em>before</em> you create your project:</p><ul><li>Do I want to use <a href="https://babeljs.io/">babel</a> or plain ES5 is good enough? Maybe <a href="http://www.typescriptlang.org/">typescript</a>? Or just <a href="https://github.com/facebook/flow">flow</a> with babel?</li><li>Do I want to use all-in-one solution or minimal framework?</li><li>If I want an all-in-one, which one? <a href="http://meanjs.org/">MEAN.js</a>? <a href="https://www.meteor.com/">Meteor</a>? New shiny <a href="http://www.nodaljs.com/">Nodal</a>?</li><li>If it’s framework — which one do I want to take? <a href="http://expressjs.com/">Express</a>? <a href="http://hapijs.com/">Hapi</a>? <a href="http://koajs.com/">Koa</a>? Something else?</li><li>Which database (and library for it) I want to use? <a href="https://www.mongodb.org/">Mongo</a>? <a href="http://redis.io/">Redis</a>? <a href="http://www.postgresql.org/">PostgreSQL</a>?</li><li>Do I need auth? Do I roll my own or use library? <a href="http://passportjs.org/">Passport.js</a>? Another one?</li></ul><p>That’s far from all the questions you’ll have to answer, but it covers the very basics.<br>Now let’s imagine you have picked your stack and it looks something like this (selection is arbitrary, things were picked mostly because that’s what I tend to use):</p><ul><li>We’ll use babel.js with ES2015 and <a href="http://babeljs.io/docs/plugins/preset-stage-2/">stage 2</a> features — rest/spread and async/await are awesome! If you don’t know how to setup babel — have a look at <a href="https://www.nathanhleung.com/article/2015/12/29/configuring-babel-6/">this guide</a>, it gives a pretty good explanation and overview of the amount of work it takes. Of course, you can always use something like <a href="https://github.com/iamstarkov/generator-babel">generator-babel</a> to ease the pain.</li><li>Let’s say we’re building very simple REST API, so we don’t need a full-blown solution like Meteor and we’ll go with <a href="http://expressjs.com/">Express.js</a>. If you don’t know how to setup Express.js project, head to their <a href="http://expressjs.com/en/starter/installing.html">official docs</a> — they are pretty good. Except that’s not all we need to do.<br>Since we’re building REST API, we’d need to handle POST, PUT, DELETE and others. To simplify those, you’ll need to plug in <a href="https://github.com/expressjs/body-parser">body-parser</a> and <a href="https://github.com/expressjs/method-override">method-override</a>. And then there’s <a href="https://github.com/expressjs/morgan">logging</a>, <a href="https://github.com/expressjs/cors">CORS</a>, <a href="https://github.com/HenningM/express-ws">websockets </a>— you get the idea.</li><li>For database we’ll pick <a href="https://www.mongodb.org/">MongoDB</a> for no reason. And we’ll use <a href="https://github.com/Automattic/mongoose">mongoose</a> as a library for interacting with it. <a href="https://docs.mongodb.org/manual/installation/">Installing</a> Mongo is not too hard if you are running modern system. Same goes for <a href="http://mongoosejs.com/docs/index.html">plugging in mongoose</a> into your app. This part is somewhat the easiest one (if you exclude defining the schema you need).</li><li>Finally, we’ll need to plug in passport.js authentication. Luckily for us, this is <a href="http://passportjs.org/docs">very easy</a> too — most of the work will be tying your DB and schema to passport.</li></ul><p>Finally! We’re done <em>setting up a project </em>for our REST API. Now we just need to write some business logic. <br>Oh, and we still need our web UI!</p><h4>Web UI</h4><p>Let’s imagine you’ve spent a couple of days and finished your basic REST API. It’s nice, fully tested (you’ve also picked the testing framework yourself!), has fancy logger and does everything you ever wanted! Now it’s time to build a new fancy web UI for it.</p><p>Once again, let’s start by looking at what questions you’ll have to answer <em>before</em> you create your UI project:</p><ul><li>Which browsers do I target? Do I need to suffer and support IE8?</li><li>Once again — do I want to use <a href="https://babeljs.io/">babel</a> or plain ES5 is good enough? Or maybe <a href="http://www.typescriptlang.org/">typescript</a>? Or just <a href="https://github.com/facebook/flow">flow</a> with babel?</li><li>Do I need module bundler? (you probably do) Which one? <a href="http://webpack.github.io/">Webpack</a>, <a href="http://jspm.io/">jspm</a>, <a href="https://github.com/rollup/rollup">rollup</a>?</li><li>What framework or library for the UI? <a href="https://angularjs.org/">Angular</a>? <a href="https://facebook.github.io/react/">React</a>? <a href="https://www.polymer-project.org/1.0/">Polymer</a>? <a href="http://cycle.js.org/">Cycle.js</a>?</li><li>If it’s not all-in-one framework, what approach and libraries do I choose for the application architecture? Time-tested <a href="http://backbonejs.org/">backbone</a>? Plain <a href="https://facebook.github.io/flux/">flux</a>? <a href="https://github.com/reactjs/redux">Redux</a>? Redux with <a href="https://github.com/yelouafi/redux-saga">sagas</a>? <a href="https://facebook.github.io/relay/">Relay</a>? DIY redux with <a href="https://github.com/Reactive-Extensions/RxJS">RxJS</a>?</li><li>Do I need CSS framework? Which one should I use? <a href="http://getbootstrap.com/">Bootstrap</a>? <a href="http://foundation.zurb.com/">Foundation</a>? <a href="https://www.getmdl.io/">Material Design Lite</a>? <a href="http://semantic-ui.com/">Semantic UI</a>?</li></ul><p>And once again — this list is far from all the questions you’ll have to answer, but it covers the very basics.<br>Now let’s imagine you have picked your stack and it looks something like this (once again, those are arbitrary and were selected purely because that’s what I tend to use):</p><ul><li>Let’s say we have a customers with up-to-date browsers, so we only have to support IE 11 and later. Which is cool — less headaches related to compatibility. And flexbox support! (well, <a href="http://caniuse.com/#search=flexbox">almost</a>)</li><li>Once again, we’ll go with babel since we already know how it works and how to set it up.</li><li>Now — module bundlers. Let’s not spend too much time picking one and stop on webpack since it provides some nifty things others don’t (e.g. <a href="https://github.com/css-modules/css-modules">css modules</a>). If you don’t know how to set it up —have a look at <a href="https://github.com/petehunt/webpack-howto">this amazing guide</a> by Pete Hunt. And be ready — it’s gonna take some time to figure everything out. But it’s totally worth it, just look at <a href="https://webpack.github.io/docs/list-of-loaders.html">all those loaders</a>!</li><li>Okay, time to pick a framework. In case you are not too familiar with the area, here’s a <a href="https://www.lullabot.com/articles/choosing-the-right-javascript-framework-for-the-job">decent overview</a> of the current major players. We’ll just stop on React.js because I like it (totally valid reason here, yup). Good thing is — setting up basic React app is <a href="https://facebook.github.io/react/docs/tutorial.html">pretty straightforward</a>. Most likely you’ll also need <a href="https://github.com/reactjs/react-router">routing</a>. And maybe <a href="https://github.com/gaearon/react-transform-boilerplate">hot reload</a>, if you want to be slightly more productive.</li><li>Here comes the fun part — architecture and underlying libraries, yay! (nay!) I’d actually encourage you to go ahead and try all of the available options if you have time — there’s a ton to learn from all of those. But, once again, for sake of simplicity let’s pick “classic” (can you call it classic already?) Flux and <a href="https://medium.com/social-tables-tech/we-compared-13-top-flux-implementations-you-won-t-believe-who-came-out-on-top-1063db32fe73#.awp2p48j6">one of many existing implementations</a>. Say <a href="https://github.com/goatslacker/alt">Alt</a> — easy to setup, pretty straightforward in use, has some nice features.</li><li>As for CSS framework — let’s just stop on Bootstrap. <a href="http://adventurega.me/bootstrap/">Everybody likes Bootstrap</a> and it plays nicely with React. Adding it to the project will only require including a .css file, which is pretty awesome.</li></ul><p>Alright then! We’re done <em>setting up a project </em>for our web UI. All we need now some business logic — easy!</p><h4>So, yeah..</h4><p>I can easily see why some people are <a href="https://medium.com/@wob/the-sad-state-of-web-development-1603a861d29f#.botpr26sy">not exactly happy</a> with the javascript ecosystem at the moment. Some even call it “<a href="https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4#.nbalbcdsg">javascript fatigue</a>”. A counterargument can be made that for developers constant learning is something everyone should be doing. While this is definitely true, unfortunately, real world does not always gives you enough space to roll at your own pace. More often than not, you need to deliver a working product within weeks if not days. So, what are possible solutions for this problem?</p><p>Probably, the most common approach is to learn one stack and use scaffolders and bootstrap projects to kickstart the development process. Specializing in one stack generally allows developers to have in-depth knowledge of all the parts and work at relatively fast pace. If the developers are familiar with CI/CD approaches, they might even set up auto-testing and auto-deployment. Problem is — that still takes a whole lot of time to do, even with help from scaffolders.</p><p>Another approach, which has started to gain traction in past few years, is to use existing Platform-as-a-Service solutions. While they do not eliminate the need to decide and learn a new stack, they generally do ease the development and deployment process quite a lot. Just look at <a href="https://www.npmjs.com/search?q=aws">all those shiny libraries</a> for AWS! Still, most of the time you end up doing some parts (e.g. UI) of the system the old way — building and deploying them yourself.</p><p>I tried doing both. And they both work just fine, but obviously have different downsides. At some point, while building yet another platform for another data-driven application demo, I started thinking — shouldn’t there be a better way? Maybe somewhat opinionated, but faster and easier way? Can we build a generic platform that can help to solve those similar use cases? So we can use it later to build apps within hours, not days?</p><h4>Core idea</h4><p>With these thoughts we set out to build a platform that will make building data-driven apps a breeze (well, at least we hope so).<br>If you look at most of the applications, you can easily split them into three simple parts:</p><ol><li>Source — something that gets or produces the incoming data.</li><li>Processor or several processors — something that reacts to that incoming data and either changes it in some way or just does something (like sending an email). Might not be present in some cases.</li><li>Renderer — simple UI that shows you nice things.</li></ol><p>If you doubt that you can describe most apps like this, here are few examples.</p><p><strong>Example 1. </strong>Product sentiment analysis using tweets<br>Input is a function that gets data from Twitter Firehose. Processor is sentiment analyzer for incoming tweets. Renderer is basic table renderer that show nice summary of sentiments.</p><p><strong>Example 2.</strong> Slack bot<br>Input is a function that gets messages from Slack. Processor is a function that, for example, searches Google using incoming message. Another processor is a function that sends response back to Slack. And optional renderer is a dashboard with all requests and responses.</p><p><strong>Example 3.</strong> Chat app<br>Input is a function that gets messages from users. Processor is not even needed in a simplest case. Renderer is a UI that shows input box and messages from the input.</p><p>And there’s <a href="https://github.com/Exynize/exynize-platform/wiki#additional-info">many more</a>. You get the idea. <br>If I would have to formally describe this logic, it’d look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b305c59d7170f8df876734b41e1091e6/href">https://medium.com/media/b305c59d7170f8df876734b41e1091e6/href</a></iframe><p>The cool thing here is that all of these things — source, processors and render — are simple functions. This means we can create a platform that allow us to easily reuse them. Not so cool thing is — functions are synchronous. What do we do if we want to work with asynchronous things? (like HTTP requests)<br>Here’s where <a href="https://github.com/Reactive-Extensions/RxJS">RxJS</a> comes to the rescue. It essentially allows us to write pretty much the same code, but adds an ability to do asynchronous things. Here’s how the logic would look using RxJS:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1bae5699deeebdb8f35108d6b8d9bc44/href">https://medium.com/media/1bae5699deeebdb8f35108d6b8d9bc44/href</a></iframe><p>I have cheated a bit, because we can’t really use exactly same functions as in the previous snippet. Source function must utilize Observer as said in <a href="https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/create.md">Rx.Observable.create</a> docs. <br>And processor must return Rx.Observable for <a href="https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/selectmany.md">flatMap</a> instead of a plain value. But adding these tiny changes allows us to work asynchronously within a function — which is pretty huge. <br>And, I had also imposed an additional constraint on the rendering function — instead of just returning HTML, it should return the <a href="https://facebook.github.io/react/">React</a> component. This will allow to easily integrate it in a final UI, plus we’ll be able to reuse a ton of <a href="http://react-components.com/">existing React components</a> within its render function without any additional hacks.</p><h4>Approach benefits</h4><p>Doesn’t all those things sound like an overcomplication? Yes and no.<br>On the one hand, adding another library or layer of abstraction always increases a cognitive burden for developers. But in this case I think that the benefits outweigh that (somewhat minor) burden, primarily because we no longer need to think about all those questions mentioned above. Let’s take a closer look at all of those benefits.</p><p>I have already mentioned first two in the previous section — asynchronicity for processors and easy integration for UI components. Let’s start with asynchronicity.</p><p><strong>Benefit 1. </strong>Asynchronous sources and processors with zero effort.<br>Being able to create functions that can handle data in an asynchronous manner out of the box without thinking about it too much a huge deal. If we’re talking about sources, we’d frequently want async sources that keep dispatching data as it comes in. For example — source of messages to Slack bot. Doing that with promises is near to impossible (because promise can only resolve once). Doing that with callbacks means it’ll be really hard (if not impossible) to use composition. Doing it with RxJS is trivial, here’s an example of Slack messages source:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c05bca4253f73c05427a61167d55e40/href">https://medium.com/media/3c05bca4253f73c05427a61167d55e40/href</a></iframe><p>This piece of code will keep dispatching Slack direction mentions until you stop it. That’s just 9 (nine!) lines of code.</p><p>Same goes for processors — we just return an RxJS observable first, then do the work and dispatch the values using the observable. And RxJS does all the work of delivering those values for us. You can find examples of processors in the tutorials in <a href="https://github.com/Exynize/exynize-platform/wiki">Exynize wiki</a>.<br>The cool thing here is that we don’t lose synchronicity — RxJS observables are synchronous by default. How awesome is that?</p><p><strong>Benefit 2. </strong>Distributed computing<br>Now, here’s the killer benefit of going with a functional approach — we can take all those functions, turn them into microservice and distribute them over several nodes. This effectively turns the code we just wrote into a full-fledged scalable microservice-based application. Which means that, if we need to, we can scale to handle some crazy amounts of data. If we have hardware.<br>I even wrote <a href="https://www.npmjs.com/package/microwork">microwork.js</a> — a library for simple creation of distributed scalable microservices in node.js based on RabbitMQ — to support this feature.</p><p>And we can still write our functions thinking (more or less) about them in a synchronous way (well, in RxJS observable way). We can still test the final application synchronously. We can even export the resulting application to a simple single javascript file if we want to.</p><h4>Exynize platform — bringing ideas together</h4><p>Using these ideas we built <a href="http://alpha.exynize.com/">Exynize</a> — a platform that allows you to easily create data-driven applications from small, reusable, single-purpose building blocks — functions.</p><p>It is, as I already mentioned, a heavily opinionated take on development of data-driven apps — after all, you will have to use javascript in general, RxJS for async things and React.js for UIs. Other than that — you are free to build whatever you want. You can follow one of our <a href="https://github.com/Exynize/exynize-platform/wiki#additional-info">tutorials</a> to build <a href="https://github.com/Exynize/exynize-platform/wiki/Tutorial:-Twitter-product-comparison">sentiment analysis for Twitter</a>, <a href="https://github.com/Exynize/exynize-platform/wiki/Tutorial:-BBC-world-news-map">heat-map of world news sentiments</a> or even a <a href="https://github.com/Exynize/exynize-platform/wiki/Tutorial:-Slack-bot">simple Slack bot</a> — give it a try.</p><p>It’s still in an early alpha stage (things can break and the platform itself is not quite stable yet), but it’s live! You can try it yourself at <a href="http://alpha.exynize.com/">alpha.exynize.com</a>.<br>And if you are interested in looking under the hood (or want to roll your own copy of it) — it’s open source and you can <a href="https://github.com/Exynize/exynize-platform">find it on Github</a>.</p><p>Try it out and let us know what you think! <br>Also, definitely <a href="https://github.com/Exynize/exynize-platform/issues">do let us know</a> if you break something! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b543dd7d3ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adopting-microservices-architecture/building-a-platform-for-serverless-data-driven-applications-with-node-js-and-microservices-4b543dd7d3ec">Building a platform for serverless data-driven applications with Node.js and microservices</a> was originally published in <a href="https://medium.com/adopting-microservices-architecture">Microservices Practitioner Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>