Answer the question
In order to leave comments, you need to log in
Vestacp: worth installing?
Hello.
The crux of the matter is, in fact, simple. Should I install Vesta to manage websites/domains on a personal server?
The fact is that Apache is currently running on Ubuntu, which I (sort of) know; I know how to make subdomains, set custom ports and then forward them to the subdomain, and so on and so forth.
But as the project expands, I see more and more that nginx is popular on the Internet, and in particular the apache + nginx bundle. I also look in the direction of the panels, which, perhaps, will simplify the task.
As a result, the question arises: is it necessary to install a panel for almost basic tasks - setting up a subdomain, forwarding a domain to a custom port (for example, domain.com:2312 will be sub.domain.com), etc.
And if it is worth putting, then on a clean system? Now I have apache, php, and elephant on ubuntu. Is it worth demolishing everything (and so reluctant) and putting everything in a new way, but putting vestacp in priority or not? or can you roll it now as ready?
I apologize in advance for the rambling question.
Answer the question
In order to leave comments, you need to log in
1) With or without panel?
If you can do without a panel, then it's better without it:
- the panel increases the attack surface. Last year, a hole was found in VestaCP, and they were asking everyone to upgrade urgently, because VestaCP servers were hacked en masse
- a panel that was supposed to simplify administration adds complexity. You will lose the ability to tune specific configs because Vesta (or another panel) will recreate them every time you edit settings from the UI. And the UI may not have what you need
2) apache + nginx
Do you need it? Apache copes with 90% of tasks even without nginx.
I had this VestaCP with Apache + Nginx. Problems:
- the site's web statistics were distorted, because I didn't figure out which web logs to use right away. The ones I set up had the correct number of hits, but they all came from the same IP.
- Server IP changed. It turned out that this is a whole problem - to bind to a new IP
- the configuration somehow fell off and PHP scripts stopped working. Couldn't figure it out. Took everything down...
For questions:
---
---
There are a couple of organizations with which I cooperate, they constantly rivet some shitty sites and the total number of domains for both exceeds a hundred. Their "programmers" don't know how to work with SSH, so I tried ispconfig first, but it turned out to be very difficult for them. I put Vesta, more than a year and a half - the flight is normal.
Since then - I put it to everyone under the "turnover", i.e. regular sites.
Recently, even a "creepy blonde" was taught to install Vesta and start domains on her. Those. the system is more than understandable.
Now, using the apache + nginx + php-fcgi bundle, I have repeatedly made sure that nginx + php-fpm is faster.
I did a comparison before and after, VDS, OS, hardware - no changes, optimal settings for resources, but the last link is still faster.
Any sites, samopis, CMS, wherever I had to transfer to a new bundle - an average increase of more than 4 times. If the php version is raised to 7.*, then the increase will be even greater and only MySQL will remain the "bottleneck".
So I advise nginx + php-fpm. But if you are going to install the php5.6 version, then you will have to slightly modify the installation script (kill the php entries with php5.6) and enable the repository for the old version before executing the script:
apt -y install software-properties-common &&
add-apt-repository -y ppa:ondrej/php &&
apt update
To configure the server to a sane state, you need to spend a lot of time.
When installing the panel, these gestures are automated.
The nginx+php-fpm bundle is no faster than nginx+apache. The difference will be noticeable on highly loaded projects. And that's not a fact.
ps From vesta refused 2 years ago. I use either ISPman or Plesk.
Vesta is very buggy. Something always falls off by itself.
But you can use it, you just have to be prepared for problems.
it’s better not to put it on a working machine, sooner or later you will have problems due to instability and there will be no one to help you
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question