diff --git a/how-to-guides/change-automatic-deployment-branch.md b/how-to-guides/change-automatic-deployment-branch.md index 108f70f..d84a99a 100644 --- a/how-to-guides/change-automatic-deployment-branch.md +++ b/how-to-guides/change-automatic-deployment-branch.md @@ -1,12 +1,12 @@ # Changing the default deployment branch -You may change the default automatic deployment branch at anytime. The default +You can change the default automatic deployment [branch](/docs/git/branches) at anytime. Your default branch is used for [automatic deployments](/docs/deployments). ## How to change the default branch 1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -2. Choose the name of the application. +2. Choose the name of your application. 3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. 4. In the horizontal tab navigation menu, choose the **Git** tab. 5. Find the **Git repository details**, island and click     @@ -17,3 +17,7 @@ branch is used for [automatic deployments](/docs/deployments). After making changes to your Git repository settings, a new deployment will begin. + +## Resources + +- [Deployments with Git](/docs/git) diff --git a/how-to-guides/change-default-composer-version.md b/how-to-guides/change-default-composer-version.md index 18bd78c..d3c8180 100644 --- a/how-to-guides/change-default-composer-version.md +++ b/how-to-guides/change-default-composer-version.md @@ -1,21 +1,21 @@ # Changing the default Composer version -You may change the default Composer version that is used for automatic deployments. +You can change the default Composer version that is used for +your automatic deployments. ## How to change the default Composer version -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application. -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Deployments** tab. -- Scroll down to the **Settings** section. -- Find the "Composer packages" switch. - +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application. +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Deployments** tab. +5. Scroll down to the **Settings** section. +6. Find the "Composer packages" switch. -- Click the **Settings** button on the far right -- Choose your desired Composer version from the dropdown -- Click **Save** +7. Click the **Settings** button on the far right +8. Choose your desired Composer version from the dropdown +9. Click **Save** -After changing the default Composer version, [automatic composer installations](/docs/deployments/automatic-composer-installs) -will use the selected version. +After changing the default Composer version, [composer](/docs/deployments/automatic-composer-installs), the version you selected is available +in your [deployment hooks](/docs/deployments/hooks). diff --git a/how-to-guides/changing-php-versions.md b/how-to-guides/changing-php-versions.md index ff6e27c..8fedcb6 100644 --- a/how-to-guides/changing-php-versions.md +++ b/how-to-guides/changing-php-versions.md @@ -1,24 +1,23 @@ # Changing PHP versions -Switching PHP versions, or upgrading to a new version can be done without launching a new instance. Although you may switch -PHP versions at anytime, a few minutes of downtime is possible. Planning for the change should be considered. Changing the -PHP version restarts the instance. +Switching [PHP versions](/docs/php), or upgrading to a new version can be done without launching a new instance. Although you may switch +PHP versions at anytime, a few minutes of downtime is possible. Planning for the change should be considered. Changing the +PHP version restarts the instance. ## How to change the PHP version -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Overview** tab. -- Scroll down to the **Application settings** section -- At the top right, click     +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Overview** tab. +5. Scroll down to the **Application settings** section +6. At the top right, click     **Change PHP version** -- Choose a PHP version -- Click "Change PHP version" +7. Choose a PHP version +8. Click "Change PHP version" ## See also [PHP](/docs/php) - diff --git a/how-to-guides/delete-domain-name.md b/how-to-guides/delete-domain-name.md index d46bcdc..2baf5d1 100644 --- a/how-to-guides/delete-domain-name.md +++ b/how-to-guides/delete-domain-name.md @@ -4,14 +4,14 @@ You may remove a domain name if you no longer need it, or if you've migrated the ## How to delete a domain name -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application. -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Domains** tab. -- From the **Domain names** section, **click** the name of the domain. -- At the top right, click     +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application. +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Domains** tab. +5. From the **Domain names** section, **click** the name of the domain. +6. At the top right, click     **Delete domain** -- When prompted, confirm. +7. When prompted, confirm. After deleting a domain name, it will no longer resolve to your application on Amezmo. Furthermore, the SSL certificate will also be purged. diff --git a/how-to-guides/deleting-applications.md b/how-to-guides/deleting-applications.md index b53c49c..c418379 100644 --- a/how-to-guides/deleting-applications.md +++ b/how-to-guides/deleting-applications.md @@ -7,11 +7,11 @@ you've terminated your application, you will no longer be charged for it. Termin You can terminate an application using the Amezmo dashboard. **To terminate an application**: -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application. -- In the horizontal tab navigation menu, choose **Overview**. -- Scroll down to the **Application details** section. -- Click **Show advanced settings** -- Click **Show more actions** -- Click the red **Terminate** button. -- Confirm your action by choosing **Terminate** from the prompt. +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application. +3. In the horizontal tab navigation menu, choose **Overview**. +4. Scroll down to the **Application details** section. +5. Click **Show advanced settings** +6. Click **Show more actions** +7. Click the red **Terminate** button. +8. Confirm your action by choosing **Terminate** from the prompt. diff --git a/how-to-guides/disable-automatic-composer-installs.md b/how-to-guides/disable-automatic-composer-installs.md index 79194a7..a59096f 100644 --- a/how-to-guides/disable-automatic-composer-installs.md +++ b/how-to-guides/disable-automatic-composer-installs.md @@ -1,15 +1,16 @@ # Turn off Automatic Composer package installations You can disable automatic Composer installations if you'd like more control over installing Composer packages. + ## How to disable automatic Composer installations -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application. -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Deployments** tab. -- Scroll down to the **Settings** section. -- Find the "Composer packages" switch +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application. +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Deployments** tab. +5. Scroll down to the **Settings** section. +6. Find the "Composer packages" switch -- Toggle the switch +7. Toggle the switch After turning off Automatic Composer installs, your next deployment will not automatically install Composer packages. diff --git a/how-to-guides/disable-automatic-laravel-migrations.md b/how-to-guides/disable-automatic-laravel-migrations.md index 3e638e2..1c862c9 100644 --- a/how-to-guides/disable-automatic-laravel-migrations.md +++ b/how-to-guides/disable-automatic-laravel-migrations.md @@ -5,15 +5,15 @@ of your application. You can disable automatic database migrations for Laravel a ## How to disable automatic Composer installations -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application. -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Deployments** tab. -- Scroll down to the **Settings** section. -- Find the "Database migrations" switch +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of your application. +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Deployments** tab. +5. Scroll down to the **Settings** section. +6. Find the "Database migrations" switch -- Toggle the switch - -After turning off Database migrations, your next deployment will not automatically run -`php artisan migrate` +7. Toggle the switch + +After turning off Database migrations, +your next [deployment](/docs/deployments) will not automatically run `php artisan migrate` diff --git a/how-to-guides/enable-automated-server-maintenance.md b/how-to-guides/enable-automated-server-maintenance.md index 961fad9..d883dde 100644 --- a/how-to-guides/enable-automated-server-maintenance.md +++ b/how-to-guides/enable-automated-server-maintenance.md @@ -4,12 +4,13 @@ You can choose a server maintenance window to automatically apply OS security up This is an automated process that Amezmo handles for you. ## Enable automatic maintenance -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Overview** tab. -- Scroll down to the **Application settings** section -- At the top right, click     + +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Overview** tab. +5. Scroll down to the **Application settings** section +6. At the top right, click     **Edit maintenance settings** -- Check or uncheck **Enable automatic maintenance** -- Click the **Save** button. \ No newline at end of file +7. Check or uncheck **Enable automatic maintenance** +8. Click the **Save** button. \ No newline at end of file diff --git a/how-to-guides/turn-off-npm-package-caching.md b/how-to-guides/turn-off-npm-package-caching.md index 6c0c044..9271cc6 100644 --- a/how-to-guides/turn-off-npm-package-caching.md +++ b/how-to-guides/turn-off-npm-package-caching.md @@ -5,15 +5,16 @@ with symbolic links, or for other reasons such as wanting to ensure that `node_m scratch on every deployment. ## Disable NPM package caching -- Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) -- Choose the name of the application. -- Above the horizontal tab navigation menu, click the Production **or** Staging tab. -- In the horizontal tab navigation menu, choose the **Deployments** tab. -- Scroll down to the **Settings** section. -- Find the NPM toggle switch. - + +1. Open the Amezmo dashboard at [https://www.amezmo.com/sites](/sites) +2. Choose the name of the application. +3. Above the horizontal tab navigation menu, click the Production **or** Staging tab. +4. In the horizontal tab navigation menu, choose the **Deployments** tab. +5. Scroll down to the **Settings** section. +6. Find the NPM toggle switch. + -- Click the switch +7. Click the switch After turning off NPM package caching, your next deployment will not use the cached `node_modules` directory. diff --git a/index.md b/index.md index 68cb07e..5495645 100644 --- a/index.md +++ b/index.md @@ -12,7 +12,7 @@ machine. That is, your application should not be hardcoded to depend on a personal file or directory. Your PHP applications on Amezmo execute in a homogeneous server environment. -Your application is deployed with [Atomic Deployments](/docs/deployments). +Your application is deployed with [Atomic PHP Deployments](/docs/deployments). Out of the box, your application should run without requiring custom packages. Amezmo creates a Docker image based on Ubuntu in advance with the most common update-to-date packages. For special requirements, please send us a