You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/els-for-libraries/browsershot/README.md
+16-53Lines changed: 16 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,20 @@
1
-
# Spatie
1
+
# Browsershot
2
2
3
-
Endless Lifecycle Support (ELS) for Spatie packages from TuxCare provides security fixes for Spatie package versions that have reached their end-of-life. This allows you to continue running your applications without vulnerability concerns, even after official support has ended.
3
+
Endless Lifecycle Support (ELS) for Browsershot from TuxCare provides security fixes for Browsershot package versions that have reached their end-of-life. This allows you to continue running your applications without vulnerability concerns, even after official support has ended.
4
4
5
5
## Supported Versions and Components
6
6
7
-
***Spatie Browsershot** 3.61.0
8
-
***Spatie Laravel Medialibrary** 9.12.4, 10.15.0
7
+
***Browsershot** 3.61.0
9
8
10
9
Other versions upon request.
11
10
12
-
## Connection to ELS for Spatie Repository
11
+
## Connection to ELS for Browsershot Repository
13
12
14
-
This guide outlines the steps needed to integrate the TuxCare ELS for Spatie packages repository into your application. The repository provides trusted Spatie packages that can be easily integrated into your **Composer** projects.
13
+
This guide outlines the steps needed to integrate the TuxCare ELS for Browsershot repository into your application. The repository provides trusted Browsershot packages that can be easily integrated into your **Composer** projects.
15
14
16
15
### Step 1: Get user credentials
17
16
18
-
You need a username and password in order to use TuxCare ELS for Spatie repository. Anonymous access is disabled. To receive the credentials, please contact [sales@tuxcare.com](mailto:sales@tuxcare.com).
17
+
You need a username and password in order to use TuxCare ELS for Browsershot repository. Anonymous access is disabled. To receive the credentials, please contact [sales@tuxcare.com](mailto:sales@tuxcare.com).
19
18
20
19
### Step 2: Configure Composer authentication
21
20
@@ -59,32 +58,15 @@ Add the `els_php_custom1` Composer repository either via CLI or by editing `comp
59
58
{ title: 'composer.json', content: composerjson }
60
59
]" />
61
60
62
-
### Step 4: Install Spatie packages
61
+
### Step 4: Install Browsershot
63
62
64
-
Install the TuxCare-maintained Spatie package release that matches your project:
65
-
66
-
<TableTabs label="Choose Spatie package: " >
67
-
68
-
<template #Spatie_Browsershot>
63
+
Install the TuxCare-maintained Browsershot release that matches your project:
**Check the exact version listed in your TuxCare Nexus account to ensure you receive the most recent patched release.**
89
71
90
72
If you edited `composer.json` manually, run `composer update` to install the package:
@@ -131,19 +113,16 @@ This allows Composer to fall back to Packagist for packages not available in the
131
113
132
114
VEX is a machine-readable format that tells you if a known vulnerability is actually exploitable in your product. It reduces false positives and helps prioritize real risks.
TuxCare provides VEX for Browsershot ELS versions: [security.tuxcare.com/vex/cyclonedx/els_lang_php/spatie-browsershot/](https://security.tuxcare.com/vex/cyclonedx/els_lang_php/spatie-browsershot/)
138
117
139
118
## How to Upgrade to a Newer Version
140
119
141
-
If you have already installed a TuxCare Spatie package and want to upgrade to a newer release, update the version string in your `composer.json` file or run the `composer require` command with the new version:
120
+
If you have already installed a TuxCare Browsershot package and want to upgrade to a newer release, update the version string in your `composer.json` file or run the `composer require` command with the new version:
0 commit comments