Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Added a "tips" section #47

Merged
merged 2 commits into from

2 participants

@simianhacker

I thought it would be nice to highlight some tips so people can avoid stubbing their toes on things. For instance I didn't realize that propagit used two ports and I was trying to run a fleet hub for each of our environments. Scratching my head when things weren't working I started to dive into the code to realize that propagit needed two ports.

Maybe the "tips" section will save some people a few cycles. :)

simianhacker added some commits
@simianhacker simianhacker Add a tips section
Even though running Fleet is pretty straight forward, if you have multiple instances running on the same server you will need to be aware that it consumes multiple ports.
aa235e7
@simianhacker simianhacker Clarified what each port is used for. f5344cf
@substack substack merged commit bf167e5 into from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Mar 27, 2013
  1. @simianhacker

    Add a tips section

    simianhacker authored
    Even though running Fleet is pretty straight forward, if you have multiple instances running on the same server you will need to be aware that it consumes multiple ports.
  2. @simianhacker
This page is out of date. Refresh to see the latest.
Showing with 5 additions and 0 deletions.
  1. +5 −0 README.markdown
View
5 README.markdown
@@ -84,6 +84,11 @@ The commands are:
For help about a command, try `fleet help <command>`.
```
+tips
+====
+
+* Fleet will acutally use two ports one for the control service and one for the git service. So if you start Fleet on port 7000 it will also use port 7001.
+
license
=======
Something went wrong with that request. Please try again.