You will need:
I'll be using Putty for this example because I'm hoping that Linux users won't need a guide on ssh'ing.
So first, download Putty from the link above (or Google it if you don't trust my links (you probably shouldn't, you don't know me)) and open run the .exe
The only relevant field in the Putty configuration window you'll need is "Host Name (or IP address)". Put your VPS's IP address in there and hit "Open".
You'll be asked for your server username (usually "root") and password, both of these you should have set up when you purchased your VPS. If you don't know these, check your emails, usually VPS sellers will contact you with the server login details when you first request a server.
Once logged in you'll be in the home directory of the user you logged in as. Usually this will be a path like /root or /home/ubuntu or /home/skel if your login user is root, ubuntu, or skel respectively.
Here we'll run a few commands to download xlarig to the server and also fetch some necessary files. From the links above, go to the xlarig releases Github page and for this guide I'll be using version v5.2.1, specifically XLArig-v5.2.1-linux-x86_64.zip. Right click the link to that zip file and copy the address. Now go back to Putty and type the following commands.
wget is used to download the xlarig miner, then unzip is used to extract this .zip file, then chmod is used to make the xlarig file able to be executed, then wget is used again to download the config file, then mv is used to rename this config file from the pastebin name to config.json, then finally ls is just used to show us all the files we've downloaded so far. Easy enough.
Right now if you ran the command...
...the miner would probably start and work fine, maybe give it a go now, you can use Ctrl + C to exit once you're happy that it's started mining. Before you leave this, you'll want to change some important settings in the config file.
With the config.json file downloaded from pastebin, you'll want to make a few changes before you start mining. The most important of these are: Setting up your wallet address, changing your thread count, and naming your miner.
Depending on which OS you installed when purchasing, different text editing software will be preinstalled on your VPS. The choices will either be "nano" or "vim". Type "nano" into your terminal, if it doesn't open try "vim". One of these will work. Because this guide is getting lengthy I won't be teaching you how to edit text files, it's a very Googleable topic. Instead we'll start with the changes you need to make.
Open your config.json file and find the section "user", currently this will have a long value something like "Svkc5vEzm..." you'll want to change this to your own wallet address. (Unless you want to mine for me instead for some reason?)
Next scroll to the section above this called "panthera", noting that we're not looking at the section that looks like "algo" : "panthera" but instead at the section that looks like "panthera" : [-1, -1, -1]. You will want to change this list of "-1" depending on how many CPU cores your VPS has. In the example case from earlier, our SkeldoorVPS server has three cores so we must have three "-1" in this list.
Lastly you will want to change your "rig-id". This is a personal name for your miner that you will use to recognise it later on the pool server. Examples could be "MyVPS" or "SkeldoorVPS-Number-1"
Something to note here is the pool server setup for this config.json is "url": "scala.party:3333" which is actually my pool for mining XLA that I'd love for you to join if you're interested in taking part in my pool party :) You can visit my pool using this link: Scala.Party If you're not interested this value can be changed too to the pool host of your choice but I'll be very sad about that.
Now running the following command will start up your miner with the correct number of threads for your VPS and start mining on Scala.Party and paying out to your wallet address.
You might realise here that if you close your Putty window or ssh session that the miner stops mining. A quick solution to this is to put "nohup" at the start of the command and "&" at the end, like this:
Doing this will force the miner to run in the background so that you can close Putty without stopping the miner process. If you're doing that I'd also recommend using the log-file command so that you can open it later to quickly check on the status of your miner. You can do this with the below command which will make a file called xla.log in your home directory for you to take a look at when needed
Tweaking your setup for best performance & how to mine forever
This page is a work in progress, I'm working on writing this section now. Come back soon.