kernicPanel
Follow
20.6K views | +3 today
kernicPanel
JavaScript, Node Js, Git, Vim, and more…
Curated by Nicolas Clerc
Your new post is loading...
Your new post is loading...
Scooped by Nicolas Clerc
Scoop.it!

semver your services with seaport :: The Universe of Discord

semver your services with seaport :: The Universe of Discord | kernicPanel | Scoop.it

Pushing out incremental changes to a service-oriented cluster can be tricky, especially when changes span multiple services. Introducing seaport, a service registry written in node.js based on semvers.

With seaport, services are brought up with a name@version string and other processes can connect to services that match a name@semver pattern.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

fabtools - Tools for writing awesome Fabric files

fabtools includes useful functions to help you write your Fabric files.

fabtools makes it easier to manage system users, packages, databases, etc.

fabtools includes a number of low-level actions, as well as a higher level interface called fabtools.require.

Using fabtools.require allows you to use a more declarative style, similar to Chef or Puppet.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

Introducing Gith - GitHub WebHooks For Node - Bocoup

GitHub offers a great feature called WebHook URLs. You can add a url to take advantage of git’s post-receive hook and get a POST request containing data related to a repository push (e.g., commits, tags, and head-resets). While the data is very detailed and thorough, its complexity and focus on mimicking the git operations make it harder to use. For example, files added are listed per commit instead of a complete array spanning all commits. Also, retreiving if a tag was added requires checking three different properties.

 

When using GitHub payloads to determine your own server behavior, different payload data from GitHub may require different actions to be taken. For example, you wouldn’t need to pull from your master branch and update a website’s content if someone pushed a new branch. But you might want to stage that branch somewhere, which would be a completely different operation.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

multi-server continuous deployment with fleet

multi-server continuous deployment with fleet | kernicPanel | Scoop.it

Writing applications as a sequence of tiny services that all talk to each other over the network has many upsides, but it can be annoyingly tedious to get all the subsystems up and running.

 

Running a seaport can help with getting all the services to talk to each other, but running the processes is another matter, especially when you have new code to push into production.

 

fleet aims to make it really easy for anyone on your team to push new code from git to an armada of servers and manage all the processes in your stack.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

sshfs-node - mount filesystem through ssh

This module helps to mount filesystem through ssh thanks sshfs. It only works with public and private keys, not with password.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

Deploying at GitHub · GitHub

Deploying is a big part of the lives of most GitHub employees. We don't have a release manager and there are no set weekly deploys. Developers and designers are responsible for shipping new stuff themselves as soon as it's ready. This means that deploying needs to be as smooth and safe a process as possible.

The best system we've found so far to provide this flexibility is to have people deploy branches. Changes never get merged to master until they have been verified to work in production from a branch. This means that master is always stable; a safe point that we can roll back to if there's a problem.

 

more...
No comment yet.