Files
server-scripts-configs/server-config-instructions.txt
2026-07-28 02:45:22 -04:00

37 lines
2.2 KiB
Plaintext

PROMPT INSTRUCTIONS FOR SETTING UP SJDEV.CO
You will set up my personal consultancy/portfolio site: https://www.sjdev.co on an AWS EC2 sentence server. The server is already running Ubuntu 24.04.3 LTS at the associated Elastic IP address: 18.119.237.252.
Read this document in its entirety before beginning to take any actions.
To the extent that you can execute all the steps described in this document without asking for approval or permission from me, do so. To the extent that you can ask only once for global/blanket permission (if needed) as opposed to making ad-hoc requests, proceed in that fashion.
Do the following:
1. SSH into the server with command:
ssh -i /Users/kjannette/.ssh/sjdev_forever.pem ubuntu@18.119.237.252
1. Run sudo apt update
2. Install: nodejs, node version manager, npm, NGINX, fail2ban
3. Run sudo apt install cmake (this will be needed because a dependency of the sjdev.co backend is FAISS)
4. Execute command sudo su root (so you can clone into the /var directory)
5. Configure NGINX sites-available/sjdev.co according to the separately-attached configuration specification.
6. Symlink the /etc/nginx/sites-avalable/sjdev.co file to sites-enabled/sjdev.co
7. Install certbot. Obtain SSL for https
8. Create and configure fail2ban file: etc/fail2ban/jail.local with standard config settings
9. The git PAT token is: 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. Configure it as a permanent env variable on the server.
10. cd /var
4. git clone https://github.com/kjannette/sjdevnext15Backend.git
5. git clone https://github.com/kjannette/sjdevnext15.git
6. cd sjdevnext15. Run: npm i
7. cd /var/sjdevnext15Backend. Run: npm i
8. Install any other dependencies and/or aproprately respond to any system messages regarding the installations
9. Install PM2. Configure pm2 to run the from and backends (consult the respective package.json) files in each repository for scripts. Save the Pm2 start configuration and also configure it to relaunch either the front or backend end int he event of a crash or a system reboot, etc
10. Disable password authentication for SSH
11. Check the browser to ensure that https://www.sjdev.co is running, reachable and is configured for https.
12. Report on the results