The initial server setup was a bit rough, primarily due to the difficulty with the Vultr dashboard's terminal and the lack of initial SSH key usage.
Go into more detail about everything that went wrong on vultr.
Recommendation: Prioritize SSH key-based authentication for security. This eliminates the need for password-based logins, which are vulnerable. Document the initial server setup steps meticulously, including firewall configuration and user creation.
We encountered difficulties using the terminal provided within the Vultr dashboard. It was not intuitive and presented some usability challenges.
To overcome the terminal limitations, we utilized the VS Code WSL bash terminal to establish an SSH connection to the IP address of the shared server. This proved to be a more efficient and familiar approach.
We used the VS Code WSL bash terminal to install Node.js, npm, and 11ty on the server. We also used it to create a new user and install Certbot for SSL certificate management.
Configuring Nginx involved creating symbolic links and setting up the sites-available directory with the project folder. This process was a bit fuzzy and required careful attention to detail.
Initially, we used WinSCP and Nano for file management. However, we found that VS Code and a proper Git workflow are more efficient and streamlined alternatives.
We experienced intermittent connection issues, possibly due to inactivity timeouts or firewall configurations. Further investigation into server-side settings and firewall rules is recommended.