Users can attach their own custom domains (example.com) or sub-domain (site.example.com) to their account using A or CNAME records. They will then be able to use these domains to view their site create via Architect.
Getting custom domains to work requires two steps:
Configuring your server so it knows what to do with custom domains (Done by you).
Updating domain DNS records to point to your server IP. (Done by user).
If first step is not completed, user will not be able to connect custom domains from Architect dashboard.
You need to configure your server so custom domains are pointed to Architect directory on your server (same directory as your main domain, where Architect files are uploaded).
When server is configured properly and and example.com domain DNS records are pointed to your server, visiting example.com should show this message:
If this message is not showing, then server is not configured correctly and user will not be able to connect this domain from Architect dashboard.
On shared hosting this is usually done by creating an Addon Domain from your cPanel (or whichever control panel your hosting provider is using) for each custom domain.
If you have access to web server (apache or nginx) configuration files on your hosting, you can configure your server to automatically point all custom domains to Architect folder, so you don't have to add addon domain for each one.
Server configuration will be different from host to host, so this guide can only provide some general examples. It cannot cover all cases.
For example, if you are on a VPS hosting that is using apache server, you can usually achieve this by modifying default apache .conf file located in /etc/apache2/sites-enabled/ folder and named 000-default.conf. Open this file with text editor and replace default path /var/www/html/ in DocumentRoot and Directory blocks with the path where BeLink is installed and restart Apache.
This is done by the customer from their domain registrar provider's website. User will be guided through this process when connecting a domain from Architect dashboard.
Server IP shown in custom domain dialog will be resolved and shown automatically in most cases, however sometimes, if you are using a proxy service you might want to manually specify IP to which users should point their custom domains via A record. This can done by setting your IP in .env configuration file in main Architect directory.
