Didn't know where to start? Here we have something might be useful.



Services section is where you can control the services inside your server. We are only tracking NGiNX, Apache2, MariaDB, Supervisord, Redis, Memcached and Beanstalkd. You can start, stop and reload any services that you want anytime.

The services page is cached for 3 minutes. If you are stop, start or reload any service, then the cache will be removed.

Automatic start stop

NGiNX, Apache2 and Supervisord will be automatically start and stop depending on usages. If you did not create any Web Application or Supervisord config, the service will automatically stop themselves.

PHP-FPM also follow this start stop rules. If you are only using Web Application with PHP7.0, PHP5.5 and PHP5.6 will stop themselves. So that you are not using more resources that you should have.


The front web server. Every static files will be served by NGiNX. Dynamic request will be pass to Apache2.


The backend web server. Every request to your Web Application will use NGiNX. If NGiNX is unable to serve them, it will be pass to Apache2. Stacking NGiNX in front of Apache will enable you to use .htaccess.

PHP will be served by Apache2 using FastCGI/FPM.


Your Relational Database Management System (RDBMS). We use MariaDB because it is a fork of MySQL and you can use any third party tools created for MySQL. Also, MariaDB is faster than MySQL (3%-5%).


Please check Supervisord section.


Redis is a in-memory key-value storage. Redis is best use to store cache data or session. Since Redis store the data inside your server’s memory, it can’t be used to store permanent data.


Memcached is use primarily for storing cache data. Same as Redis, Memcached store the data inside server’s memory.


Beanstalkd is used to store work queue. You can store your work queue such as sending email and crunching uploaded images to Beanstalkd. Then you need to write your logic to pull data from Beanstalkd and running the task in the background.