A next generation open source platform as a service (PaaS)
Go JavaScript Shell CSS HTML Ruby Other
Latest commit 4e7a7fe Jan 18, 2017 @lmars lmars host: Repair MongoDB cluster before the controller
So that it is started with the volume from the previous primary when
rebooting a single node cluster.

Fixes #3847.

Signed-off-by: Lewis Marshall <lewis@lmars.net>
Permalink
Failed to load latest commit information.
Godeps vendor: Updates for Flynn images Nov 4, 2016
appliance appliance/mongodb: Fix dumping empty databases Jan 12, 2017
blobstore all: Switch to SquashFS + OverlayFS images Nov 4, 2016
bootstrap logaggregator,bootstrap: Use ports and service name from env Dec 15, 2016
cli cli: Rewrite app name in service from process config Jan 12, 2017
controller scheduler: Increase HTTP timeout to 10s Jan 12, 2017
dashboard dashboard: Fix creating app releases in dashboard (#3793) Dec 29, 2016
demo Vagrantfile: Ensure network cable is connected Jan 3, 2017
discoverd all: Switch to SquashFS + OverlayFS images Nov 4, 2016
docker-receive docker-receive: Fix converting AUFS whiteouts Nov 23, 2016
docs docs: Update Linode vanilla kernel instructions Dec 19, 2016
flannel all: Switch to SquashFS + OverlayFS images Nov 4, 2016
gitreceive slugbuilder: Determine process types in Go Dec 24, 2016
host host: Repair MongoDB cluster before the controller Jan 19, 2017
installer installer: Fix iptables rules Jan 8, 2017
logaggregator logaggregator,bootstrap: Use ports and service name from env Dec 15, 2016
pinkerton all: Switch to SquashFS + OverlayFS images Nov 4, 2016
pkg pkg/pinned: Use a retry dialer Jan 12, 2017
router router: Don't allow routes to bind to HTTP ports Jan 12, 2017
schema schema: Remove entries for non-existent sink examples Jan 17, 2017
script script: Generate backups with non-resolving domains Jan 13, 2017
slugbuilder slugbuilder: Bump buildpacks Jan 15, 2017
slugrunner all: Switch to SquashFS + OverlayFS images Nov 4, 2016
status all: Switch to SquashFS + OverlayFS images Nov 4, 2016
taffy all: Switch to SquashFS + OverlayFS images Nov 4, 2016
test test/cluster2: Run host cleanup on the correct host Jan 13, 2017
updater controller: Associate releases with a single app Dec 14, 2016
util test/cluster2: Run cluster on a single host Jan 12, 2017
vendor vendor: Fix creating EC2 keypair (#3651) Nov 9, 2016
.gitignore all: Switch to SquashFS + OverlayFS images Nov 4, 2016
CONTRIBUTING.md docs: Fix missing Google Style Guide link Oct 27, 2016
LICENSE all: Update Flynn trademark status Apr 7, 2015
MAINTAINERS all: Add Joseph to MAINTAINERS Oct 14, 2015
Makefile Makefile: Fix running tests which require root Nov 14, 2016
PRIVACY.md docs: Update privacy policy Sep 22, 2016
README.md Readme: Add link into Development Guide Aug 11, 2016
Tupfile.ini all: Replace Makefiles with Tupfiles, update .gitignores Aug 3, 2014
Tuprules.tup all: Switch to SquashFS + OverlayFS images Nov 4, 2016
Vagrantfile Vagrantfile: Ensure network cable is connected Jan 3, 2017
docs.gemspec all: Remove website (docs and schema remain in new locations) Feb 24, 2015
schema.gemspec all: Remove website (docs and schema remain in new locations) Feb 24, 2015
tup.config tup: Fix default image repository URI Feb 11, 2015

README.md

Flynn logo

Flynn is an open source Platform as a Service

Flynn is designed to run anything that can run on Linux, not just stateless web apps. Flynn comes with highly available database appliances, including PostgreSQL, MySQL, and MongoDB.

Eventually we want Flynn to be the only tool developers and ops teams need to develop, deploy, and manage running software.

You can learn more about Flynn at our website.

The Flynn website also has documentation.

Status

Flynn is very actively developed by Prime Directive, Inc. and the Flynn community.

Learn more about Flynn's stability.

Learn more about Flynn's security.

We want to know if you run into any unexpected behavior. Please report issues on this repository after searching to see if anyone has already reported the issue.

Getting Started

Run your own cluster

Flynn includes an installer that supports most major cloud providers.

If you want to setup and run your own Flynn cluster (either locally, on dedicated hardware or using a cloud provider) take a look at the Installation Guide.

Deploying applications

Check out the Flynn Basics guide for instructions on deploying and scaling applications.

Contributing

We welcome and encourage community contributions to Flynn.

We have specific priorities for development. Pull requests that do not address these priorities may not be accepted.

Please familiarize yourself with the Contribution Guide before contributing.

You can install Flynn development environment and tools by following the Development Guide.

There are many ways to help Flynn besides contributing code:

  • Find bugs and file issues.
  • Improve the documentation and website.

Contact us

We want to hear about any trouble, success, delight, or pain you experience when using Flynn. Let us know by filing an issue, joining the mailing list, joining us in IRC (#flynn on Freenode), or emailing us.

Flynn® is a trademark of Prime Directive, Inc.