This is an attempt to propose an optimal standard subdomain name pattern for WikiSuite users.
Goals:
- A predictable recipe we can all use
- For new users not to be worried of having done it wrong
- Use this for scripting projects like the WikiSuite Orchestrator
- Permit to move some services to different servers if needed later (WikiSuite is designed to run on one server by default which is fine at the beginning)
- Offer a predictable setup for all websites on a Virtualmin server (Taking into account Servers vs Sub-Servers)
- Make it easy to create clones and test upgrades via https://doc.tiki.org/Manager
- Use standards to help automatically detect / configure apps.
Virtualmin admin panel
https://server.example.org:10000 : Virtualmin admin panel
- To do: Test handling of visiting IP address or server.example.org
- Ideally, nothing is shown unless we configure it explicitly.
Why not use example.org:10000? This permits to set up a new Virtualmin server without affecting an existing website (ex.: if you already have a running site, and you want to set all this up in parallel, and migrate the website once everything is tested)
In fact, since port 10000 can sometimes be blocked, we'd want management.server.example.org as an alternative to server.example.org:10000
But server.* is not a good pattern because if we had:
- server.example.org
- server.example.com
- server.wikisuite.org
- server.wikisuite.net
and we logged into all servers in SSH, we would see root@server for each...
Websites
Say we host example.org
We will pick example as a username.
What | domain name | where files are stored | |
Tiki Manager | manager.example.org | /home/example/tiki-manager/tiki-manager.php and /home/example/public_html/ | Top-level Virtual Server (Others are Sub-Servers) |
main website | example.org | /home/example/domains/example.org/public_html/ | |
test upgrade | next.example.org | /home/example/domains/next.example.org/public_html/ | data from prod, code from trunk |
staging | staging.example.org | /home/example/domains/staging.example.org/public_html/ | data from prod, code from tip of branch |
Backup of a week ago | oneweekago.example.org | /home/example/domains/oneweekago.example.org/public_html/ | exact copy from 7 days ago |
Ad hoc copy | 20170431-11h55.example.org | /home/example/domains/20170431-11h55.example.org/public_html/ | On demand exact copy |
todo :mail / MX: example.org
CalDAV and CardDAV
http://sabre.io/dav/service-discovery/
Openfire / XMPP
conference.example.org
Instead of https://example.org:7443/ofmeet/, we want https://ofmeet.example.org/ofmeet/ or even better: https://ofmeet.example.org/
http://wikisuite.org/How-to-install-Openfire-Meetings-on-ClearOS#Avoiding_non-standard_ports