Ubuntu Installer

[KeiroD]

Hi,

So, I've got the installer via the Install link here... and when I go to actually install it, the script says the following:

root@starlight:~# ./vst-install.sh
cut: /etc/redhat-release: No such file or directory
grep: /etc/redhat-release: No such file or directory
Error: sorry, we currently support RHEL and CentOS only

So, your installer currently does not have Ubuntu support. However I see that someone else here has successfully gotten Ubuntu working.

Any suggestions as to get this working on Ubuntu?

Incidentally, why not use Webmin's OS detection script? You could use that to detect as many Linux distributions as possible and possibly even have the installer call other scripts that would allow you to install specific packages for specific distros.

Additionally, I'd like to note that it's nice to know that there's support for WHMCS... but given WHMCS's security issues of late, perhaps you could also support Hostbill as well?

[Graham]

I started with this post:

http://stevetan.me/post/ubuntu-13-04-vestacp-setup

[KeiroD]

I started with this post:

http://stevetan.me/post/ubuntu-13-04-vestacp-setup

Ah, my thanks, friend Graham. :)

Edit: Works quite nicely. Now, to mess with it and see if I can actually roll it out for my company.

[Graham]

I started with this post:

http://stevetan.me/post/ubuntu-13-04-vestacp-setup

Ah, my thanks, friend Graham. :)

All credit to Steve Tan :-)

[KeiroD]

I started with this post:

http://stevetan.me/post/ubuntu-13-04-vestacp-setup

Ah, my thanks, friend Graham. :)

All credit to Steve Tan :-)

Indeed. My thanks for pointing out where I could check out Steve's work for Vesta. His guide for this is very short, very easy to understand, which is important if you want to get the server up and running quickly.

[SteveTan86]

Ah, my thanks, friend Graham. :)

All credit to Steve Tan :-)

Indeed. My thanks for pointing out where I could check out Steve's work for Vesta. His guide for this is very short, very easy to understand, which is important if you want to get the server up and running quickly.

Glad it was useful for someone. There's some other stuff you should take note of though.

For example, Vesta's default configuration for DKIM is to use 512 bit keys (that was until version 0.9.8-5 when they increased it to 1024 bits by default), but you should really be using at least a 1024 bit key and a 2048 bit key would be the best choice. However, that being said, Vesta doesn't support anything more than 1024 bits at the moment, they will have to rewrite the DNS scripts for this.

Maybe when I have some time over the weekend, I'll write a guide for this.

[KeiroD]

Indeed. My thanks for pointing out where I could check out Steve's work for Vesta. His guide for this is very short, very easy to understand, which is important if you want to get the server up and running quickly.

Glad it was useful for someone. There's some other stuff you should take note of though.

For example, Vesta's default configuration for DKIM is to use 512 bit keys (that was until version 0.9.8-5 when they increased it to 1024 bits by default), but you should really be using at least a 1024 bit key and a 2048 bit key would be the best choice. However, that being said, Vesta doesn't support anything more than 1024 bits at the moment, they will have to rewrite the DNS scripts for this.

Maybe when I have some time over the weekend, I'll write a guide for this.

Noted. I was not aware that Vesta does not support anything more than 2048-bit keys. I've been testing VestaCP, though unfortunately, I had to stop my testing a day ago due to needing to move my testing environment.

Please do write a guide, as that will be very useful to everyone that decides to use your guide. That said, may I echo your guide(s) to my own documentation as well?

Skid: You should see if you can also have it support 4096-bit keys, as 2048 ones will probably be soon dropped in favor for the newer bit length.

[skid]

KeiroD, yeah absolutely.

[SteveTan86]

Indeed. My thanks for pointing out where I could check out Steve's work for Vesta. His guide for this is very short, very easy to understand, which is important if you want to get the server up and running quickly.

Glad it was useful for someone. There's some other stuff you should take note of though.

For example, Vesta's default configuration for DKIM is to use 512 bit keys (that was until version 0.9.8-5 when they increased it to 1024 bits by default), but you should really be using at least a 1024 bit key and a 2048 bit key would be the best choice. However, that being said, Vesta doesn't support anything more than 1024 bits at the moment, they will have to rewrite the DNS scripts for this.

Maybe when I have some time over the weekend, I'll write a guide for this.

Noted. I was not aware that Vesta does not support anything more than 2048-bit keys. I've been testing VestaCP, though unfortunately, I had to stop my testing a day ago due to needing to move my testing environment.

Please do write a guide, as that will be very useful to everyone that decides to use your guide. That said, may I echo your guide(s) to my own documentation as well?

Skid: You should see if you can also have it support 4096-bit keys, as 2048 ones will probably be soon dropped in favor for the newer bit length.

Feel free to include the guide(s) wherever you want, as long as you link back to the original guide(s).

[KeiroD]

Awesome, thanks Steve! :)