Installation
The below installation steps assume that you’ve already spun up a new Virtual Machine on your favorite KVM cloud network. Your server should have Ubuntu 20.04 LTS installed with at least 1GB+ RAM and at least 1 CPU core before proceeding.
It is also imperative that you do not install any “container” applications such as Docker or Kubernetes. Ready? Let’s go!
Last updated: Jan 24, 2021
Quick install (if you want to use the setup wizard):
cd /tmp/ && wget -O ss slick.fyi && bash ss…or if you prefer manually setting up your SlickStack configuration, do this instead:
wget -O /tmp/ss-config http://mirrors.slickstack.io/bash/ss-config-sample.txtmkdir -p /var/www/ && cp /tmp/ss-config /var/www/ss-config && nano /var/www/ss-configcd /tmp/ && wget -O ss slick.fyi && bash ssNeed some help? Contact one of our SlickStack Experts anytime or check out their paid gigs on Upwork, Fiverr, Legiit, etc. You can also review our ever-expanding documentation or join our free chat room communities on Skype, Discord, or Gab.
SSL Warning: CloudFlare should be activated on your domain prior to SlickStack installation, otherwise the self-signed OpenSSL certificate will result in “insecure” errors displaying when your website is loaded in a browser (after the installation is complete). CloudFlare’s free SSL Certificate Authority pairs with OpenSSL and “signs” the self-signed origin certificate with zero issues, which usually takes only a few minutes or less…
Alternatively, if you are planning to use Lets Encrypt instead of OpenSSL, you don’t necessarily need CloudFlare, and Certbot should still be able to verify your server using the temporary self-signed OpenSSL certificate that SlickStack uses for initial Nginx configuration. However, be sure to point both the staging and dev subdomains in your DNS records before beginning the SlickStack installation if you will be using the staging/dev site features, otherwise Certbot will be unable to verify the SSL certificate for those subdomains.