Cloud | On-Premises | |
All Builder Functions | + | + |
White Label | + | + |
Website builder location | Site.pro雲 | Your own server |
Your Clients Websites Location | 100% in Hosting Datacenter | |
範本 | 190+ | 190+ |
自定義範本 | + | |
Private Plugins | + | |
工具欄自定義(獨特的圖示、顏色、主題) | + | |
Automatic backups | + |
All published websites (95% HTML / 5% PHP) are located in Hosting Provider's data center.
登入您的伺服器控制面板.
點擊“建站工具”創建網站
創建網站並點擊“發布”.
Connect Your Domain
位於主機商的伺服器中.
The publication process is the process which starts when the client presses button "Publish" in builder toolbar. The process can be divided into several parts which are executed one after another in specified order:
Note that practically all these steps are executed quite quickly and usually client does not see them all in publication process bar.
Builder plugin is a module for hosting control panel (cPanel, Plesk, etc.) which is installed on panel and displayed for end clients as an extra button among other buttons. The builder button can be customized with your own icon and title.
The builder plugin works as a gateway from panel to site builder. Plugin purpose is to retrieve all required information of client account from hosting control panel (using internal API) and pass it to site builder. The required information includes:
After plugin collects information it calls builder via API and pass information for it. Builder checks the license of your hosting server and determines whether to let you in or not. If the license is verified then builder API returns URL otherwise it returns error message. In case if plugin gets URL from builder it redirects the client by this URL to builder where client can construct his website. If the license verification fails then builder returns error message "License is required" meaning that the license could not be detected by API call and provided parameters (check how to fix this error).
The communication between builder plugin and builder is made via HTTP port 80 or 443 depending what protocol builder uses. In case if you use Cloud builder then 443 port is always used. If you use On-Premises builder then it depends on what protocol your builder is running on.
When the client opens builder for the first time then builder suggests to choose a template first before starting constructing website. During website construction all website data is saved in special ".dat" files in builder storage and all media files which client uploads are also stored in builder. Note that during website construction in builder no changes are made on client's hosting. Changes are applied only when client presses button "Publish" in builder toolbar — then builder generates real website files (consisting of .php, .js, .css and other files) and publishes them to client's hosting via FTP connection (see how publication works in more details).
When the client next time opens builder then builder finds his ".dat" files and loads them instead of offering to choose template anew. Note that when client opens builder then builder does not download client's current website files from hosting — builder has all website data in his own storage.
The identification of website in builder is made only by domain. It means that the client can have multiple websites in his account (addon domains, sub-domains) and construct websites in builder separately for all of them. If client's domain is renamed further then it also must be renamed in builder separately. Otherwise the client will be offered to choose template anew as if the website was opened for the first time.
If you have your own hosting control system for your customers and do not use predefined hosting control panel which we support then you can also use site builder by implementing your own plugin using builder API method to create session.
Site.pro recommends On-Premises licence because of stability reason: