-
Notifications
You must be signed in to change notification settings - Fork 11
Installation on VPS
- [THIS DOES NOT WORK YET. FOLLOWING THE CONFIGURATION *NOW* MAKES THE GUI ACCESSIBLE BY ANYONE WHO KNOWS YOUR VPS URL](You don't need to use Git to download, but it makes it so much easier to update)
Git should already be installed, check if it is by opening the terminal and using the command git -v.
Download from https://nodejs.org/.
Once Git is installed, navigate to the location where you want the gui to be. For this example we'll just install it in the default root folder, /root/, which is where most people also have their bot. Then use the command git clone https://github.com/ZeusJunior/tf2-automatic-gui.git. Once it is done, the gui is available in a new folder called tf2-automatic-gui. Navigate to it using the command cd tf2-automatic-gui
Run the command npm i after you've navigated to the bot folder.
Configuration on a VPS is a little different
In order for the GUI to access your bots files, you need to make a slight change to the /tf2-automatic-gui/resources/paths.js file. Currently the top part of it looks like this:
const folders = {
config: './config'
};You need to change that to your bots folder. For example if it is installed in the root folder:
const folders = {
config: '/root/tf2-automatic/files/<botusername>'
};The GUI runs on port 3000. You can allow your vps to accept this port by running the command:
sudo ufw allow 3000
Then start the GUI using PM2 by navigating to the GUI folder (cd tf2-automatic-gui) and typing pm2 start app --name GUI, the GUI is now running on your vps and you can access it by going to http://<yourvpsip>:3000/
Currently you still need to remember to restart your bot when you are done using the gui.
When done, head over to usage. You can skip the configuration part there. As it is configured differently on VPS