From 66c99cae0f83a613c9385270f2fa70ce1d4af3c3 Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 11:59:36 +0200 Subject: [PATCH 1/9] Update horizon.md --- horizon.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/horizon.md b/horizon.md index 51ced5bed9c..cdf07c9fc42 100644 --- a/horizon.md +++ b/horizon.md @@ -105,6 +105,18 @@ When upgrading to a new major version of Horizon, it's important that you carefu In addition, you should re-publish Horizon's assets: php artisan horizon:publish + +To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file: + + { + "scripts": { + "post-autoload-dump": [ + "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", + "@php artisan package:discover --ansi", + "@php artisan horizon:publish --ansi" + ] + } + } ## Running Horizon From e11743d07a61962677f3e8832be10793e3d8bfed Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 12:02:54 +0200 Subject: [PATCH 2/9] Update telescope.md --- telescope.md | 26 ++++++++++++++++++++------ 1 file changed, 20 insertions(+), 6 deletions(-) diff --git a/telescope.md b/telescope.md index 451614bae2c..d1d7c9bab54 100644 --- a/telescope.md +++ b/telescope.md @@ -5,6 +5,7 @@ - [Configuration](#configuration) - [Data Pruning](#data-pruning) - [Migration Customization](#migration-customization) +- [Upgrading Telescope](#upgrading-telescope) - [Dashboard Authorization](#dashboard-authorization) - [Filtering](#filtering) - [Entries](#filtering-entries) @@ -50,12 +51,6 @@ After installing Telescope, publish its assets using the `telescope:install` Art php artisan migrate -#### Updating Telescope - -When updating Telescope, you should re-publish Telescope's assets: - - php artisan telescope:publish - ### Installing Only In Specific Environments If you plan to only use Telescope to assist your local development, you may install Telescope using the `--dev` flag: @@ -111,6 +106,25 @@ Without pruning, the `telescope_entries` table can accumulate records very quick By default, all entries older than 24 hours will be pruned. You may use the `hours` option when calling the command to determine how long to retain Telescope data. For example, the following command will delete all records created over 48 hours ago: $schedule->command('telescope:prune --hours=48')->daily(); + + +## Upgrading Telescope + +When upgrading to a new version of Telescope, you should re-publish Telescope's assets: + + php artisan telescope:publish + +To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file: + + { + "scripts": { + "post-autoload-dump": [ + "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", + "@php artisan package:discover --ansi", + "@php artisan telescope:publish --ansi" + ] + } + } ## Dashboard Authorization From 999c4192011d59a5f14370d72fae7fdf7d3c62a8 Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 12:05:02 +0200 Subject: [PATCH 3/9] Update horizon.md --- horizon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/horizon.md b/horizon.md index cdf07c9fc42..d87b4b5410f 100644 --- a/horizon.md +++ b/horizon.md @@ -102,7 +102,7 @@ Horizon exposes a dashboard at `/horizon`. By default, you will only be able to When upgrading to a new major version of Horizon, it's important that you carefully review [the upgrade guide](https://github.com/laravel/horizon/blob/master/UPGRADE.md). -In addition, you should re-publish Horizon's assets: +In addition, when upgrading to any new Horizon version, you should re-publish Horizon's assets: php artisan horizon:publish From efeca1b4aa946a91bb9f11276b883e5d266ebf4f Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 12:06:28 +0200 Subject: [PATCH 4/9] Move navigation --- telescope.md | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/telescope.md b/telescope.md index d1d7c9bab54..42859bcc4c8 100644 --- a/telescope.md +++ b/telescope.md @@ -5,8 +5,8 @@ - [Configuration](#configuration) - [Data Pruning](#data-pruning) - [Migration Customization](#migration-customization) + - [Dashboard Authorization](#dashboard-authorization) - [Upgrading Telescope](#upgrading-telescope) -- [Dashboard Authorization](#dashboard-authorization) - [Filtering](#filtering) - [Entries](#filtering-entries) - [Batches](#filtering-batches) @@ -106,28 +106,9 @@ Without pruning, the `telescope_entries` table can accumulate records very quick By default, all entries older than 24 hours will be pruned. You may use the `hours` option when calling the command to determine how long to retain Telescope data. For example, the following command will delete all records created over 48 hours ago: $schedule->command('telescope:prune --hours=48')->daily(); - - -## Upgrading Telescope - -When upgrading to a new version of Telescope, you should re-publish Telescope's assets: - - php artisan telescope:publish - -To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file: - - { - "scripts": { - "post-autoload-dump": [ - "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", - "@php artisan package:discover --ansi", - "@php artisan telescope:publish --ansi" - ] - } - } -## Dashboard Authorization +### Dashboard Authorization Telescope exposes a dashboard at `/telescope`. By default, you will only be able to access this dashboard in the `local` environment. Within your `app/Providers/TelescopeServiceProvider.php` file, there is a `gate` method. This authorization gate controls access to Telescope in **non-local** environments. You are free to modify this gate as needed to restrict access to your Telescope installation: @@ -148,6 +129,25 @@ Telescope exposes a dashboard at `/telescope`. By default, you will only be able } > {note} You should ensure you change your `APP_ENV` environment variable to `production` in your production environment. Otherwise, your Telescope installation will be publicly available. + + +## Upgrading Telescope + +When upgrading to a new version of Telescope, you should re-publish Telescope's assets: + + php artisan telescope:publish + +To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file: + + { + "scripts": { + "post-autoload-dump": [ + "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", + "@php artisan package:discover --ansi", + "@php artisan telescope:publish --ansi" + ] + } + } ## Filtering From 3ed5cedd08bbe86a42effcc7606a4837e8fdd59b Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 13:07:29 +0200 Subject: [PATCH 5/9] Update horizon.md --- horizon.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/horizon.md b/horizon.md index d87b4b5410f..7379d0c5428 100644 --- a/horizon.md +++ b/horizon.md @@ -110,9 +110,7 @@ To keep the assets up-to-date and avoid issues in future updates, we highly reco { "scripts": { - "post-autoload-dump": [ - "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", - "@php artisan package:discover --ansi", + "post-update-cmd": [ "@php artisan horizon:publish --ansi" ] } From 8ea9991c7962b104147cce8fadce45298700eee3 Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 13:07:45 +0200 Subject: [PATCH 6/9] Update telescope.md --- telescope.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/telescope.md b/telescope.md index 42859bcc4c8..de0fba0c9ad 100644 --- a/telescope.md +++ b/telescope.md @@ -141,9 +141,7 @@ To keep the assets up-to-date and avoid issues in future updates, we highly reco { "scripts": { - "post-autoload-dump": [ - "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", - "@php artisan package:discover --ansi", + "post-update-cmd": [ "@php artisan telescope:publish --ansi" ] } From 362421c84188cecb6566fcecb95578cd62e84d42 Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 13:15:54 +0200 Subject: [PATCH 7/9] Update horizon.md --- horizon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/horizon.md b/horizon.md index 7379d0c5428..3e865ef2e38 100644 --- a/horizon.md +++ b/horizon.md @@ -106,7 +106,7 @@ In addition, when upgrading to any new Horizon version, you should re-publish Ho php artisan horizon:publish -To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file: +To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-update-cmd` scripts in your `composer.json` file: { "scripts": { From 6edd2fe06653143a6469734b006b658fcf8b7ebd Mon Sep 17 00:00:00 2001 From: Dries Vints Date: Thu, 6 Aug 2020 13:16:11 +0200 Subject: [PATCH 8/9] Update telescope.md --- telescope.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/telescope.md b/telescope.md index de0fba0c9ad..dbdcf80d193 100644 --- a/telescope.md +++ b/telescope.md @@ -137,7 +137,7 @@ When upgrading to a new version of Telescope, you should re-publish Telescope's php artisan telescope:publish -To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file: +To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-update-cmd` scripts in your `composer.json` file: { "scripts": { From 6174fbc8ffa2d8859c90ce4628e94ff860bc377d Mon Sep 17 00:00:00 2001 From: Taylor Otwell Date: Fri, 7 Aug 2020 10:04:18 -0500 Subject: [PATCH 9/9] formatting --- horizon.md | 4 ++-- telescope.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/horizon.md b/horizon.md index 3e865ef2e38..0deb43c26c5 100644 --- a/horizon.md +++ b/horizon.md @@ -105,8 +105,8 @@ When upgrading to a new major version of Horizon, it's important that you carefu In addition, when upgrading to any new Horizon version, you should re-publish Horizon's assets: php artisan horizon:publish - -To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-update-cmd` scripts in your `composer.json` file: + +To keep the assets up-to-date and avoid issues in future updates, you may add the command to the `post-update-cmd` scripts in your `composer.json` file: { "scripts": { diff --git a/telescope.md b/telescope.md index dbdcf80d193..d9ff5dcb4bc 100644 --- a/telescope.md +++ b/telescope.md @@ -129,7 +129,7 @@ Telescope exposes a dashboard at `/telescope`. By default, you will only be able } > {note} You should ensure you change your `APP_ENV` environment variable to `production` in your production environment. Otherwise, your Telescope installation will be publicly available. - + ## Upgrading Telescope @@ -137,7 +137,7 @@ When upgrading to a new version of Telescope, you should re-publish Telescope's php artisan telescope:publish -To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-update-cmd` scripts in your `composer.json` file: +To keep the assets up-to-date and avoid issues in future updates, you may add the `telescope:publish` command to the `post-update-cmd` scripts in your application's `composer.json` file: { "scripts": {