> 3. Use of the Software.<p>> 3.1. Use. You may authorize employees, agents, and subcontractors to use the Software in accordance with this Section 3, so long as you remain responsible for them. You may make a reasonable number of copies of the Software for back-up and archival purposes.<p>> You acknowledge that the Software is a preview offering not intended for production environments, and you agree that you will only use the Software in non-production environments.<p>Anyway, all that stuff in the docs is lovely, but if you just want to have a look:<p><pre><code> pip install gsutil
gsutil cp -r gs://alloydb-omni-install/$(gsutil cat gs://alloydb-omni-install/latest) .
</code></pre>
The install scripts are only 16K, look at `installer/scripts/start_alloydb.sh` for more, but basically it just runs the two docker containers listed in <a href="https://cloud.google.com/alloydb/docs/omni/install#install" rel="nofollow">https://cloud.google.com/alloydb/docs/omni/install#install</a><p>Seems kind of weird, having a one-time install script to prep a machine (but only a specific type of machine!) that you then run a pair of docker containers on to me, honestly. Eventually consistent deployment states? eh. whatever...