![]() NX_CLOUD_APP_URL can be set with an HTTP or HTTPS url.NX_CLOUD_APP_URL should be accessible from your CI and dev machines.You will need to know the URL that the Nx Cloud installation can be accessed by (see NX_CLOUD_APP_URL below).( This is not necessary if you are running the file server separately. You will need to create a directory on the host machine where data will be stored.Otherwise, you will likely want to run Nx Cloud using HTTPS. If you have a proxy/load-balancer in front of Nx Cloud, you will likely want to run Nx Cloud using HTTP (the proxy/load-balancer will handle TLS). Step 2: Create a Containerĭepending on how your infrastructure is set up, you can either run Nx Cloud using HTTPS or HTTP. To update the version of Nx Cloud, pull the new version of the image and run it against the same mount (see below). > docker pull nxprivatecloud/single-image The instructions will go through running the embedded file server, and then, at the end, will talk about hosting your cached artefacts on an external service, such as Amazon S3. For that, we created the nxprivatecloud/nx-cloud-mongo image. Either by using a service such as Mongo Atlas.You will then need to host the database separately: Using a single container is the easiest way to set it up, but it isn't the most robust way to run Nx Cloud. This document covers the latter version.īy default, the container created by the nxprivatecloud/single-image image will create two of them: the stateless Nx Cloud service, and the file server. The flags and the capabilities are the same between the two, but the Kubernetes setup is more robust and better documented. Using a single standalone container (NOT RECOMMENDED).Using Kubernetes (several containers working together).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |