Advanced install settings

hi everyone!

The (bottom of the page) has a very convenient form for selecting components. I 'm sure it makes sense to do the same for

  1. It is convenient - copied the installation command - the system quietly installed the necessary components, do not answer questions during installation

  2. New users will immediately see - what components are in the panel, what dependencies between them - more meaningful to choose

But the option “* * To perform an unattended installation (with defaults): * *” I strongly do not like

// sorry for translation from russian :wink:

UPD: I made my page based on the site of Vesta

1 Like

Hi @egorka

Welcome to the forum :slight_smile:.

Please have a look at the custom part in our github readme page:

1 Like


is already available:

1 Like

It 's not the same. The VESTA’s form specifies a logical relationship between components, for example, you cannot select apache and php-fpm at the same time. Your form is not user friendly

I also don 't understand the meaning of the “Force installation” flag, how it differs from “Interactive install”.

This is by design, Hestia sticks on phpfpm in all cases now, also for apache2.

It is not our form, it was provided from an external user - but please explain, why do you think, that it is not user friendly.

Force is force - it will disable validation checks and allows you basicly to run the install twice. Interactive means that you not will be asked for questions, but you need to add hostname, mail and a admin password. Both settings are also available in vesta with the same conditions.

I don 't have full knowledge of component dependencies :wink:

This form is created for professionals who understand exactly what components and what they need.

For beginners it would be good to make a form of like VESTA, taking into account all combinations of components, as well as sections FTP, MAIL, DNS and so on to group components

// I see that translated poorly, but i cannot formulate correctly

i use the following command and it works perfectly:
bash --multiphp yes -f -y no -e [email protected] -p password -s hostname.domain

All important components are included.

This form is of great importance for promoting the HestiaCP.

Personally, how I chose the VESTA: I came in, I chose the components I wanted, I turned off those that were not needed at all (dns and mail), I set the administrator 's data - in a convenient web form, not in a sad console, I copied this “magic installation string” to the putty - I got a finished dashboard! There was no limit to my joy that day!

  • I learned about the existence of putty 2 days earlier :wink:

No nod documentation, no “github trips,” a minimum of interaction with the “terrible black console”: looked at what the panel “can” chose, installed - the perfect recipe.

The same I wanted from the heir of the VESTA ) but had to go to the documentation (

People need extremely simple solutions, people are afraid of the console)

I understand what you mean, but this is basicly not the target user group for hestia - no offens at all!

Everyone needs to start somewhere, for hestia we decided to push a solution for known sysadmins - that’s why the notification post comes from: Please read this, before you start!

Your script is good, but look at the page of vesta - there all components are arranged in blocks that do not allow to choose, for example, 2 ftp servers at the same time.
And your script is a separate page that no one knows about.
Hestia needs a form similar to the vesta on the home page of the site :wink:

It is difficult for me to understand) I always try to focus any interface on beginners

Api access to the form of generation of the installation command - it is overreaction))

Interactive - Is it a quiet mode? I thought on the contrary i would be asked all with this parameter)

Force - Does not have a second YES/NO parameter? It 's different from everyone else

I meant something like this: - I took the code from the main page of the vesta, corrected a little - the curve is framed, and the force parameter needs to be reworked… does not work in my firefox ( and it gives “–force no” - this will disable the force?

I leveled the blocks on the form

And corrected the logic of force - it has no value yes/no


Check my page, please)

1 Like