From de9620759af3c41236f2a6f103770a5d07c3e560 Mon Sep 17 00:00:00 2001 From: DeaDvey Date: Sat, 2 Nov 2024 10:50:42 +0000 Subject: [PATCH] readme shit --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 4ad587c..19dde62 100755 --- a/README.md +++ b/README.md @@ -33,23 +33,23 @@ This project utilizes Apache2 as a reverse proxy to handle incoming web traffic To set up Apache2 as a reverse proxy for your Node.js app: - Start your Node.js application (/node/app.js) on port 8003. You can run the application in a tmux session using the command: + 1. Start your Node.js application (/node/app.js) on port 8003. You can run the application in a tmux session using the command:
``` node app.js``` - Edit the Apache configuration file /etc/apache2/sites-enabled/000-default.conf and add the following lines to forward requests to the Node.js app: + 2. Edit the Apache configuration file /etc/apache2/sites-enabled/000-default.conf and add the following lines to forward requests to the Node.js app:
-```ProxyPass / http://localhost:8003/``` +```ProxyPass / http://localhost:8003/```
- If you have other sites or applications running on Apache2 that should not be proxied to Node.js, you can add exceptions like this: + 3. If you have other sites or applications running on Apache2 that should not be proxied to Node.js, you can add exceptions like this:
-```ProxyPass /wordpress !``` +```ProxyPass /wordpress !```
- Replace /wordpress with the appropriate path for your exception. + Replace /wordpress with the appropriate path for your exception:
-Testing +## Testing To verify that the Node.js application is running and accessible through Apache2, you can use the curl command: