or “Why the ther team will make your job with Docker harder”
During my internship, I got to play with Docker, which is quite impressive in terms of ease of use, but also in terms of performances. The technology behind it feels rock solid (but maybe that’s just marketing! 😉 ).
Please check out this post if you don’t know Docker already.
There are some Docker images containerizing OS’s (Ubuntu, Debian) but also for software, like MySQL or OpenVPN. Users can use any of these images as a base for their own custom images. It means that the user will be able to add stuff to an existing environment to create their own microservice.
Docker is a containerization technology that gained in popularity lately. It allows developers to ship their software with all its dependencies in a VM-like environment with a controlled configuration.
The main difference with VMs is that Docker uses the host machine kernel, instead of emulating one for each VM. It allows to instantiate multiple Docker images in containers on the same host without requiring gigantic amounts of resources.
Let’s see how Docker simplifies the development of on-demand services.
As TypeScript is implementing a great number of the ES6 (ECMAScript6) standards, it is important to stay up-to-date with the latest specification updates.
In particular, the module feature is getting central for all framework and libraries developers (me included), who need to be able to package properly their code. and thus how to correctly use them in TypeScript.
If you are using Travis CI to automate the build of a TypeScript, that’s a problem you probably encountered. As Travis CI can allow you to automatically build in various environment, TSD is hitting hard on the GitHub API, which can cause the “GitHub rate limit reached” message to appear.
The solution is quite simple, you’ll have to create a GitHub token and add it in Travis as an environment variable. This tutorial will also work with any build automation system that support environment variables.