Hacker News new | past | comments | ask | show | jobs | submit login

> 3. Use of the Software.

> 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.

> 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.

Anyway, all that stuff in the docs is lovely, but if you just want to have a look:

    pip install gsutil
    gsutil cp -r gs://alloydb-omni-install/$(gsutil cat gs://alloydb-omni-install/latest) .
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 https://cloud.google.com/alloydb/docs/omni/install#install

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...




For those who want to skip the gsutil part, that bucket and its keys are public:

    curl -vJLO https://storage.googleapis.com/alloydb-omni-install/$(curl -fs https://storage.googleapis.com/alloydb-omni-install/latest)alloydb_omni_installer.tar.gz
The `latest)alloy` is not a typo, the contents of the "latest" file ends with a slash and GCS doesn't tolerate `//` (presumably just like S3 wouldn't)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: