Include "/opt/bitnami/apps/myapp/conf/nf"Ĭreate and edit the /opt/bitnami/apps/myapp/conf/nf file and add the following lines: $ sudo mkdir /opt/bitnami/apps/myapp/confĬreate and edit the /opt/bitnami/apps/myapp/conf/nf file and add the following lines: Alias /myapp/ "/opt/bitnami/apps/myapp/htdocs/"Īlias /myapp "/opt/bitnami/apps/myapp/htdocs/" $ sudo mkdir /opt/bitnami/apps/myapp/htdocs/ Run the following commands to create the directories: $ sudo mkdir /opt/bitnami/apps/myapp These steps assume that your application will live in the /opt/bitnami/apps/myapp/ directory: To create a custom HTTP-only application, such as an AngularJS application that only requires an HTML index page, a CSS file and a Javascript file, follow the steps below. Restart the Apache server: $ sudo /opt/bitnami/ctlscript.sh restart apache SSLCertificateKeyFile "/opt/bitnami/apache/conf/bitnami/certs/server.key" SSLCertificateFile "/opt/bitnami/apache/conf/bitnami/certs/server.crt" bitnami.Ĭreate and edit the /opt/bitnami/apache/conf/vhosts/nf file and add the following lines: NOTE: Replace the USER placeholder with the system username, i.e. Run the following commands to create the directory: $ mkdir -p ~/projects/myappĬreate and edit the /opt/bitnami/apache/conf/vhosts/nf file and add the following lines: NOTE: These steps assume that your application will live in the ~/projects/myapp/ directory: This example shows how to create a custom HTTP-only application, such as an AngularJS application that only requires an HTML index page and a CSS file and a Javascript file. Specify one or more alternate compose files (default: docker-compose.NOTE: If you are running a Bitnami MEAN stack version prior to 4.2.5-1 check the specific section, since major changes were introduced in that version. File should be in yaml or json format and suffixed with respective file extension. Specify a file from which to read environment variables. Specify an alternate Rancher compose file (default: rancher-compose.yml) Update interval in milliseconds (default: 1000) Number of containers to upgrade at once (default: 2) Rollback to the previous deployed version Upgrade regardless if service has changedĬonfirm that the upgrade was success and delete old containers Remove services in the stack that do not exist in current compose file Options Nameīefore doing the upgrade do an image pull on all hosts that have the image already The rancher up command is similar to the Docker Compose up command. Note: The service name will always include the stack name to ensure that we’re referencing the correct service. # Stop by name of service, container, host $ rancher stop / # Stop by ID of service, container, host $ rancher stop NameĬlient configuration file (default $’ Whenever you use the rancher command, there are different global options that you can use. Shows a list of commands or help for one command Wait for resources service, container, host, stack, machine, projectTemplate View details for service, container, host, environment, stack, volume Stop or deactivate service, container, host, stack Start or activate service, container, host, stack Set number of containers to run for a service Rancher CLI Commands NameĮxport configuration yml for a stack as a tar archive or to local filesĭelete service, container, stack, host, volume The Rancher CLI is able to manipulate environments, hosts, stacks, services and containers in Rancher. These docs are for Rancher 1.6, if you are looking for Rancher 2.x docs, see here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |