• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

How to make builder.MyDomain.com behave more like horde: webmail.*ClientDomain.com ??

mariano81

New Pleskian
Right now, in order for plesk clients/domain admins to login to their suitebuilder sites, they go to: http://builder.MyDomain.com/Login . For For Horde, they go to http://webmail.ClientDomain.com . Wouldn't it make sense to make the sitebuilder app as avaliable as Horde? This way, they can go to http://builder.TheirDomain.com, just like with horde they go to http://webmail.TheirDomain.com.

What kind of changes would the plesk, site builder community admins would have to make in order to make this happen?

I am thinking something like:

Editing the zz011_sitebuilder.conf, located in /etc/httpd/conf.d/zz011_sitebuilder.conf ??

Editing the zz10_psa_httpd.conf, located in /etc/httpd/conf.d/zz10_psa_httpd.conf ??

executing the sb_config command "sb_config --sb_hostname=builder.* --force_update_wscfg" ??

For those of us using Plesk's DNS Bind, creating a dns template "A" record "sitebuilder.<domain>" with a value of "<IP>" ??

How can I make this work? Very relevant in terms of giving white/private label resellers a more of a white/private label solution...

Any takers?
 
Try to change Sitebuilder configuration file in this way /etc/httpd/conf.d/zz011_sitebuilder.conf:
...............
DocumentRoot /usr/local/sitebuilder/htdocs
ServerName builder
ServerAlias builder.*
...............
...............
After that restart apache and check it up. You need also create appropriate DNS records for all domains which will use builder.domain.tld as access point to Sitebuilder so it could be resolved properly.
 
Back
Top