DirectAdmin Installer variables

[DrWizzle]

A new build is released. It fixes an issue in the Evolution menu customization page when trying to set a custom menu icon for a category.

I've just done another DA install, and the setup script threw out some more variables I didn't know existed. Are the DA_ADMIN_USER and DA_ADMIN_PASSWORD variables actually used for the admin when used? This could prove very useful.

Also what's DA_ETH_DEV? Asking as there's no mention of these on the install help page (unless it's in your to do list)

Overview | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

 

[Richard G]

Also what's DA_ETH_DEV?

Short for ethernet_dev from directadmin.conf https://docs.directadmin.com/directadmin/general-usage/all-directadmin-conf-values.html#ethernet-dev

Are the DA_ADMIN_USER and DA_ADMIN_PASSWORD variables actually used for the admin when used?

Yes interesting question, because is that indeed for the admin user or the da_admin user used for database?

 

[DrWizzle]

Short for ethernet_dev from directadmin.conf https://docs.directadmin.com/directadmin/general-usage/all-directadmin-conf-values.html#ethernet-dev

Yes interesting question, because is that indeed for the admin user or the da_admin user used for database?

Thanks Richard

 

[fln]

These installer variables allow changing the default admin account (used to log-into DA after installer is finished) user name and password.

Database password is always auto-generated. A custom database password can be used if ./conf/mysql.conf file is created before starting DA installer. In this case the credentials specified in this file will be used.


Short installer help is available with /usr/local/directadmin/scripts/setup.sh --help command.

 

[zEitEr]

I've just done another DA install, and the setup script threw out some more variables I didn't know existed. Are the DA_ADMIN_USER and DA_ADMIN_PASSWORD variables actually used for the admin when used? This could prove very useful.

When I defined the variables before running setup.sh:

[root@alma-4gb-nbg1-2 ~]# export DA_ADMIN_USER=poralix
[root@alma-4gb-nbg1-2 ~]# export DA_ADMIN_PASSWORD=iMl***************Lmt
[root@alma-4gb-nbg1-2 ~]# export DA_HOSTNAME=server.example.net

I got: the following information has been set:

  Admin username:     poralix
  Admin password:     iMl***************Lmt
  Admin email:        [email protected]
  Server Hostname:    server.example.net

If you cannot connect to the login URL, then it is likely that a firewall is blocking port 2222.

Nice)

 

[DrWizzle]

When I defined the variables before running setup.sh:

[root@alma-4gb-nbg1-2 ~]# export DA_ADMIN_USER=poralix
[root@alma-4gb-nbg1-2 ~]# export DA_ADMIN_PASSWORD=iMl***************Lmt
[root@alma-4gb-nbg1-2 ~]# export DA_HOSTNAME=server.example.net

I got: the following information has been set:

  Admin username:     poralix
  Admin password:     iMl***************Lmt
  Admin email:        [email protected]
  Server Hostname:    server.example.net

If you cannot connect to the login URL, then it is likely that a firewall is blocking port 2222.

Nice)

Cheers @zEitEr , I didn't have time to spin up another vps and try it. I think that's a cracking feature though as with those env variables, would be easier now to create install scripts to set variables to what I want. Really nice touch.