The next section “Configuration” shows all available options to configure the server.
This section shows how to get a (static) HTTP website up and running quickly.
(For HTTPS, see the Installation instructions)
Starting Swiftfire for the first time
When Swiftfire is started, nothing much will seem to happen… after all, it is a server. Just point a browser to: “localhost:6678/serveradmin” and hit return.
Next you will be greeted with a spartan setup screen that asks you to setup an administrator account and to point the root for the administration site to the ‘sfadmin’ directory that is included in the distribution. After submitting, reload the screen and the server admin setup pages show themselves.
Adding and enabling domain
First login to the server admin account at: localhost:6678/serveradmin
Select the menu “Domains -> Manage Domains”
Type the full name of the domain to be added (i.e. including the domain extension like “.com”, “.org” or “.co.uk”) in the text field. Then click the “Create Domain” button.
Note: do not include ‘www’ if BOTH domains (with and without ‘www’) must be created.
Next, click the ‘Edit’ link after the new domain name to complete the setup.
If the domain should also be reachable when using the ‘www’ prefix, set that property to ‘true’.
Note that in the current version we need to cycle through the “Domain Management” after every change.
Next, set the root directory for the domain. This is the directory that contains the ‘index’ file of the site.
Then set the “Enabled” entry to ‘true’.
That is all, the website can now be reached.
When the settings are correct, make sure to save the domain on the server side by selecting the “Save To File” button on the “Domain -> Manage Domains” page.
Choosing a service port
The website will be active as soon as Swiftfire started. But it is reachable at port 6678, which is probably not what is needed. Provided no other server is running on port 80, change the “HttpServicePortNumber” of Swiftfire to port 80:
- Select the “Parameters” page.
- For the “HttpServicePortNumber” enter the value “80” then click “Update”.
Alternatively keep port 6678 and add a forwarding rule to the server running on port 80 to port 6678 for the domain(s) you will be servicing with Swiftfire.
Make sure the parameters are saved by clicking the “Save to File” button.
If the port number was changed, a restart of the server is necessary. Click the “Restart” button on the “Home” page.
Localhost & Browsers
There is a little snag in the HTTP protocol that makes it necessary to use a little trick when viewing a website on your own server when the domain is not registered yet.
Most (all?) browsers will use the host name in the URL field as the host they want to reach. To reach that host they will perform a domain-lookup with a DNS. When that domain is not know, it cannot be accessed. Even when that domain is hosted on the same computer the browser is running on.
While it is possible to edit the “etc/host” file (and others?), it is simpler to change the name in the URL to “localhost” and create an alias domain called “localhost” on the “Domains -> Manage Domains” page. Simply duplicate the entry that was made above, but now for the domain name “localhost”. No domain extension (like .com etc) needed.