I had a long discussion yesterday with Colin about some of the pain
points that are causing him to currently have a separate atomic-
workstation build on the Centos infrastructure, and what we can do to
address those and consolidate back to the Fedora infrastructure.
The long term goal we have is getting to the point where someone who is
moderately adventuresome can consume Fedora Atomic Workstation in a
rolling fashion - every week a new version of Atomic Workstation shows
up with whatever minor or major updates are considered stable, and if
something breaks, rpm-ostree offers the ability to roll back.
Here's my personal definition of "moderately adventuresome":
1. Build a virtual machine. I need this to work on GNOME Boxes and Windows 10 Pro Hyper-V, so I'll probably use the Atomic Host ISO. I do *not* need or want any VirtualBox or Vagrant stuff.
2. Start up the VM full-screen (GNOME Boxes / Virtual Machine Manager on Linux, the Hyper-V Viewer on Windows)
3. "git clone" some repo that has all the code to layer Atomic Workstation onto an Atomic Host. Run it and voila!
4. Create SSH keys, post the public key to GitHub/GitLab/Bitbucket, "git clone" my own projects and have at it!
I can find documentation for 1; I tried the test composes of Atomic Workstation ISOs but couldn't get one to work, so I want to do my own builds inside a VM. But I haven't been able to find the step 3 anywhere.