Step By Step Setting up a GoLilyPad Server (SSH) [CentOS]

This is how to install GoLilyPad on CentOS with SSH.​

Getting Java:
First of all, you need Java. Its very easy to get Java. Just use this command to get Java. Make sure you download the latest version which is 7 for now.

Code (text):

yum install java7

Getting screens (Optional):
To get more overview over the running servers, you can use Screens. Screens gives you the ability to run applications without letting your terminal session open. To get screens, use this command:

Code (text):

yum install screen

- Basic commands:
Create a new screen session: screen -S <name of session>
Leaving a screen: Press: Ctrl-a + Ctrl-\
Returning back to a screen: screen -r <name of session>
List of all your screens: screen -ls
List of all the screen commands: Press: Ctrl-a ?
Setting everything up:
I recommend you to create two folders: Connect & Proxy. You can do this easily in the SSH with these commands:

Code (text):

mkdir Connect

Code (text):

mkdir Proxy

Or you can make these 2 folders by using FTP.

- Setting up GoLilyPad Connect:
After that, go to your Connect folder.

Code (text):

cd Connect

Or use a screen:

Code (text):

screen -S Connect

- - Getting the files:
Now comes the importent step of all: You need to know if your CentOS is 64 or 32 bit. If you are using the 64-bit version of CentOS, use this command:

Code (text):

wget http://ci.lilypadmc.org/job/Go-Server-Connect/lastSuccessfulBuild/artifact/target/connect-linux-amd64

If you're using the 32-bit version of CentOS, use this command:

Code (text):

wget http://ci.lilypadmc.org/job/Go-Server-Connect/lastSuccessfulBuild/artifact/target/connect-linux-386

- - Set the right file permissions:
You got the file. Now you have to set the file permissions right. Otherwise it won't work. If you're using 64-bit, use this command:

Code (text):

chmod +x connect-linux-amd64

If you're using 32-bit, use this command:

Code (text):

chmod +x connect-linux-386

- - Run for the first time:
We can now run the connect part of LilyPad. Use this command for the 64-bit version:

Code (text):

./connect-linux-amd64

Use this command for the 32-bit version:

Code (text):

./connect-linux-386

Now stop the server by typing: Stop or Halt.

- - Edit the connect config:
There are 2 ways to do this. You can use FTP and edit the file, or you can use SSH. If you want to change it by using SSH, do the following:

Code (text):

vi connect.yml

You'll see the config right now. You might seem a bit confused, but it is actually very simple. You will need to change the following:

Code (yaml):

logins:
- username: example
  password: example
 

The first Username and Password are for the LilyPad proxy. So you can fill them in by yourself. You'll need this later in the process. The the other ones are for the Bukkit servers.
Example:

Code (yaml):

bind: :5091

logins:
- username: LilyPad
  password: password
- username: hub
  password: hubserverpw
- username: factions
  password: facserverpw
 

Do that each time if you add a server. Make sure that the username and password equals to the username and password of the Bukkit-Connect config! If you have errors while starting the Connect, then check your configuration on syntax mistakes.

- Setting up GoLilyPad Proxy:
Go to your Proxy folder you made earlier. (Make sure you are back in the folder where the connect and proxy folders are).

Code (text):

cd Proxy

Or use a screen:

Code (text):

screen -S Proxy

- - Getting the files:
Also here you need to know if you are running 64 or 32 bit. If you're running 64-bit, use this command:

Code (text):

wget http://ci.lilypadmc.org/job/Go-Server-Proxy/lastSuccessfulBuild/artifact/target/proxy-linux-amd64

If you're using the 32-bit version of CentOS, use this command:

Code (text):

wget http://ci.lilypadmc.org/job/Go-Server-Proxy/lastSuccessfulBuild/artifact/target/proxy-linux-386

- - Set the right file permissions:
You got the file. Now you have to set the file permissions right. Otherwise it won't work. If you're using 64-bit, use this command:

Code (text):

chmod +x proxy-linux-amd64

If you're using 32-bit, use this command:

Code (text):

chmod +x proxy-linux-386

- - Run for the first time:
We can now run the connect part of LilyPad. Use this command for the 64-bit version:

Code (text):

./proxy-linux-amd64

Use this command for the 32-bit version:

Code (text):

./proxy-linux-386

You will get an error that is spamming a bit, so try to stop the server with Stop or Halt.

- - Edit the connect config:
There are 2 ways to do this. You can use FTP and edit the file, or you can use SSH. If you want to change it by using SSH, do the following:

Code (text):

vi proxy.yml

The config will look like this:

Code (yaml):

connect:
  address: 127.0.0.1:5091
  credentials:
    username: example
    password: example
proxy:
  bind: :25565
  routes:
  - domain: ""
    server: example
  locale:
    full: The server seems to be currently full. Try again later!
    offline: The requested server is currently offline. Try again later!
    loggedIn: You seem to be logged in already. Try again later!
    lostConn: Lost connection... Please try to reconnect
    shutdown: The server is being restarted. Please try to reconnect
  motd: A LilyPad Server
  maxPlayers: 1
  authenticate: true
 

Its very easy to edit this file. This is what you need to know:

Code (yaml):

credentials:
    username: LilyPad
    password: password

This needs to equal to the settings we changed in the connect.yml. You can find the same settings back if you scroll up.

Code (yaml):

routes:
  - domain: ""
    server: hub

In the other version of LilyPad you had to put a Wildcard (*). Now you don't have to put anything. Just leave it "". Server is the server where you connect to. So like the Hub server. Also that needs to equal to the username of the Hub bukkit-connect config.

Code (yaml):

motd: A LilyPad Server

To use color codes, use the symbol &!

And now...
You're done! First start GoLilyPad-Connect and then GoLilyPad-Proxy. It should run fine. If not, post a thread in the Support section

Video:
@sgtcaze Made a awesome video tutorial on how to do this. Thanks!

​

1. Can you please describe the question more?
2. Yes.
3. No you don't have to

Whopppsss.. My bad.. Forgot to update that..

Regexp = Username

Thread updated. It should be good now.

What are you logs saying? Look to them all