Skip to content

Commit 2fd245b

Browse files
authored
Update README.md
1 parent 390e05a commit 2fd245b

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

README.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,32 @@
1-
# PhNode Project
1+
# Phnode Project
22

3-
Welcome to the PHNode Project repository. This project is designed to facilitate reliable and consistent access to the latest Long Term Support (LTS) version of Node.js across various platforms. By caching Node.js versions directly in this repository, we aim to mitigate potential workflow disruptions caused by direct downloads from nodejs.org.
3+
Welcome to the Phnode Project repository. This project is designed to facilitate reliable and consistent access to the latest Long Term Support (LTS) version of Node.js across various platforms. By caching Node.js versions directly in this repository, we aim to mitigate potential workflow disruptions caused by direct downloads from nodejs.org.
44

55
## Overview
66

77
This repository:
88

9-
Pulls the latest LTS version of Node.js from nodejs.org for different operating systems and architectures.
10-
Caches these Node.js binaries to provide faster and more reliable access.
11-
Automatically updates the cache with each minor version release within the current LTS line.
9+
* Pulls the latest LTS version of Node.js from nodejs.org for different operating systems and architectures.
10+
* Caches these Node.js binaries to provide faster and more reliable access.
11+
* Automatically updates the cache with each minor version release within the current LTS line.
1212

13-
## Why PHNode?
13+
## Why Phnode?
1414

1515
Downloading Node.js directly from the official nodejs.org server during automated workflows and deployments can sometimes lead to issues such as network instability, server downtime, or rate limiting. By caching the Node.js binaries in this repository, we aim to provide a more robust solution that ensures your workflows remain uninterrupted.
1616
How to Use
1717

1818
To make use of the cached Node.js binaries in your projects, follow the instructions below:
1919

20-
Find the Required Version: Navigate through the repository to find the specific version of Node.js that you need for your platform.
21-
22-
Download: Click on the relevant file and use the Download button to obtain the binary.
23-
24-
Integrate: Integrate the downloaded Node.js binary into your project or workflow as you would normally.
20+
1. Find the Required Version: Navigate through the repository to find the specific version of Node.js that you need for your platform.
21+
2. Download: Click on the relevant file and use the Download button to obtain the binary.
22+
3. Integrate: Integrate the downloaded Node.js binary into your project or workflow as you would normally.
2523

2624
## Automatic Updates
2725

28-
The PHNode repository is configured to automatically fetch and update the cache whenever a new minor version of the current LTS line of Node.js is released. This ensures that you always have access to the most up-to-date and stable version for your development and production needs.
26+
The Phnode repository is configured to automatically fetch and update the cache whenever a new minor version of the current LTS line of Node.js is released. This ensures that you always have access to the most up-to-date and stable version for your development and production needs.
2927
Contributing
3028

31-
If you would like to contribute to the PHNode project or report issues, please feel free to open a pull request or submit an issue through the GitHub repository.
29+
If you would like to contribute to the Phnode project or report issues, please feel free to open a pull request or submit an issue through the GitHub repository.
3230
License
3331

3432
This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). For more information, please see the LICENSE file in this repository.

0 commit comments

Comments
 (0)