These docs should cover the entire lifecycle of your CoreOS machines. Anyone can submit changes to these docs via GitHub. For more in-depth support, jumping into #coreos on IRC, emailing the dev list or filing a bug are recommended.
CoreOS runs on most cloud providers, virtualization platforms and bare metal servers. Running a local VM on your laptop is a great dev environment. Following the Quick Start guide is the fastest way to get set up.
Follow these guides to connect your machines together as a cluster. Configure machine parameters, create users, inject multiple SSH keys and more with cloud-config. Providing a discovery token via cloud-config is the easiest way to get a cluster set up.
CoreOS aggregates individual machines into a single pool of resources. Instead of running a service on a specific machine, services are submitted to the cluster and the cluster manager, fleet, decides where they should run. Fleet allows you to gracefully update CoreOS across your cluster, handles machine failures automatically and allows for efficient resource utilization.
Configuration values are distributed within the cluster for your applications to read. Values can be changed programatically and smart applications can reconfigure automatically. You'll never have to run Chef on every machine in order to change a single config value ever again.
Most users will never have to build CoreOS from source or modify it in any way. If you have a need to modify CoreOS, we provide an SDK that allows you to build your own developer images. We also provide OEM functionality for cloud providers and other companies that need to customize CoreOS to run within their environment.