Skip to content

Convert a few posts to Markdown #2437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SEWeiTung merged 1 commit into from
Sep 3, 2019
Merged

Convert a few posts to Markdown #2437

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
82 changes: 48 additions & 34 deletions locale/en/blog/module/multi-server-continuous-deployment-with-fleet.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,51 +8,64 @@ slug: multi-server-continuous-deployment-with-fleet
layout: blog-post.hbs
---

<p><img style="float:right;margin-left:1.2em;" alt="substack" src="http://substack.net/images/substackistan.png"><i>This is a guest post by James "SubStack" Halliday, originally posted <a href="http://substack.net/posts/16a9d8/multi-server-continuous-deployment-with-fleet">on his blog</a>, and reposted here with permission.</i></p>
_This is a guest post by James "SubStack" Halliday, originally posted [on his blog](http://substack.net/posts/16a9d8/multi-server-continuous-deployment-with-fleet), and reposted here with permission._

<p>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. </p>
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.

<p>Running a <a href="http://substack.net/posts/7a1c42">seaport</a> 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. </p>
Running a [seaport](http://substack.net/posts/7a1c42) 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.

<p><a href="http://github.com/substack/fleet">fleet</a> 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. </p>
[fleet](http://github.com/substack/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.

<p>To start using fleet, just install the fleet command with <a href="https://npmjs.com">npm</a>: </p>
To start using fleet, just install the fleet command with [npm](https://npmjs.com):

<pre style="">npm install -g fleet </pre>
```
npm install -g fleet
```

<p>Then on one of your servers, start a fleet hub. From a fresh directory, give it a passphrase and a port to listen on: </p>
Then on one of your servers, start a fleet hub. From a fresh directory, give it a passphrase and a port to listen on:

<pre style="">fleet hub --port=7000 --secret=beepboop </pre>
```
fleet hub --port=7000 --secret=beepboop
```

<p>Now fleet is listening on :7000 for commands and has started a git server on :7001 over http. There's no ssh keys or post commit hooks to configure, just run that command and you're ready to go! </p>
Now fleet is listening on :7000 for commands and has started a git server on :7001 over http. There's no ssh keys or post commit hooks to configure, just run that command and you're ready to go!

<p>Next set up some worker drones to run your processes. You can have as many workers as you like on a single server but each worker should be run from a separate directory. Just do: </p>
Next set up some worker drones to run your processes. You can have as many workers as you like on a single server but each worker should be run from a separate directory. Just do:

<pre style="">fleet drone --hub=x.x.x.x:7000 --secret=beepboop </pre>
```
fleet drone --hub=x.x.x.x:7000 --secret=beepboop
```

<p>where <span class="code">x.x.x.x</span> is the address where the fleet hub is running. Spin up a few of these drones. </p>
where `x.x.x.x` is the address where the fleet hub is running. Spin up a few of these drones.

<p>Now navigate to the directory of the app you want to deploy. First set a remote so you don't need to type <span class="code">--hub</span> and <span class="code">--secret</span> all the time. </p>
Now navigate to the directory of the app you want to deploy. First set a remote so you don't need to type `--hub` and `--secret` all the time.

<pre style="">fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop </pre>
```
fleet remote add default --hub=x.x.x.x:7000 --secret=beepboop
```

<p>Fleet just created a <span class="code">fleet.json</span> file for you to save your settings. </p>
Fleet just created a `fleet.json` file for you to save your settings.

<p>From the same app directory, to deploy your code just do: </p>
From the same app directory, to deploy your code just do:

<pre style="">fleet deploy </pre>
```
fleet deploy
```

<p>The deploy command does a <span class="code">git push</span> to the fleet hub's git http server and then the hub instructs all the drones to pull from it. Your code gets checked out into a new directory on all the fleet drones every time you deploy. </p>
The deploy command does a `git push` to the fleet hub's git http server and then the hub instructs all the drones to pull from it. Your code gets checked out into a new directory on all the fleet drones every time you deploy.

<p>Because fleet is designed specifically for managing applications with lots of tiny services, the deploy command isn't tied to running any processes. Starting processes is up to the programmer but it's super simple. Just use the <span class="code">fleet spawn</span> command: </p>
Because fleet is designed specifically for managing applications with lots of tiny services, the deploy command isn't tied to running any processes. Starting processes is up to the programmer but it's super simple. Just use the `fleet spawn` command:

<pre style="">fleet spawn -- node server.js 8080 </pre>
```
fleet spawn -- node server.js 8080
```

<p>By default fleet picks a drone at random to run the process on. You can specify which drone you want to run a particular process on with the <span class="code">--drone</span> switch if it matters. </p>
By default fleet picks a drone at random to run the process on. You can specify which drone you want to run a particular process on with the `--drone` switch if it matters.

<p>Start a few processes across all your worker drones and then show what is running with the <span class="code">fleet ps</span> command: </p>
Start a few processes across all your worker drones and then show what is running with the `fleet ps` command:

<pre style="">fleet ps
```
fleet ps
drone#3dfe17b8
├─┬ pid#1e99f4
│ ├── status: running
Expand All @@ -61,18 +74,20 @@ drone#3dfe17b8
└─┬ pid#d7048a
├── status: running
├── commit: webapp/1b8050fcaf8f1b02b9175fcb422644cb67dc8cc5
└── command: node server.js 8889</pre>
└── command: node server.js 8889
```

<p>Now suppose that you have new code to push out into production. By default, fleet lets you spin up new services without disturbing your existing services. If you <span class="code">fleet deploy</span> again after checking in some new changes to git, the next time you <span class="code">fleet spawn</span> a new process, that process will be spun up in a completely new directory based on the git commit hash. To stop a process, just use <span class="code">fleet stop</span>. </p>
Now suppose that you have new code to push out into production. By default, fleet lets you spin up new services without disturbing your existing services. If you `fleet deploy` again after checking in some new changes to git, the next time you `fleet spawn` a new process, that process will be spun up in a completely new directory based on the git commit hash. To stop a process, just use `fleet stop`.

<p>This approach lets you verify that the new services work before bringing down the old services. You can even start experimenting with heterogeneous and incremental deployment by hooking into a custom <a href="http://substack.net/posts/5bd18d">http proxy</a>! </p>
This approach lets you verify that the new services work before bringing down the old services. You can even start experimenting with heterogeneous and incremental deployment by hooking into a custom [http proxy](http://substack.net/posts/5bd18d)!

<p>Even better, if you use a service registry like <a href="http://substack.net/posts/7a1c42">seaport</a> for managing the host/port tables, you can spin up new ad-hoc staging clusters all the time without disrupting the normal operation of your site before rolling out new code to users. </p>
Even better, if you use a service registry like [seaport](http://substack.net/posts/7a1c42) for managing the host/port tables, you can spin up new ad-hoc staging clusters all the time without disrupting the normal operation of your site before rolling out new code to users.

<p>Fleet has many more commands that you can learn about with its git-style manpage-based help system! Just do <span class="code">fleet help</span> to get a list of all the commands you can run. </p>
Fleet has many more commands that you can learn about with its git-style manpage-based help system! Just do `fleet help` to get a list of all the commands you can run.

<pre style="">fleet help
Usage: fleet &lt;command&gt; [&lt;args&gt;]
```
fleet help
Usage: fleet <command> [<args>]

The commands are:
deploy Push code to drones.
Expand All @@ -85,8 +100,7 @@ The commands are:
spawn Run services on drones.
stop Stop processes running on drones.

For help about a command, try `fleet help `.</pre>
For help about a command, try `fleet help`.
```

<p><span class="code">npm install -g fleet</span> and <a href="https://github.com/substack/fleet">check out the code on github</a>! </p>

<img src="http://substack.net/images/fleet.png" alt="fleet" width="849" height="568">
`npm install -g fleet` and [check out the code on github](https://github.com/substack/fleet)!
Loading