Releases: Balancingrock/Swiftfire
Linux and a commenting system
Release 1.3.0 introduced a commenting system and was a pretty big change overall. Aside from the comment system it also introduced the possibility to have multiple instances of Swiftfire running in parallel. This is very convenient if you run Swiftfire on a development machine.
Our website at http://swiftfire.nl is still being updated to detail this release.
Since then 1.3.1 and 1.3.2 have removed a few bugs that had crept in up to release 1.3.2.
Now 1.3.3 has been released which also completes the addition of the Linux platform for development and deployment. However we ourselves do not use the Linux platform for development (or deployment) thus we depend on you to report any issue's that you might have.
Release 1.2.1
Release 1.2.1 adds the sources for the server admin account, adds additional logging when server parameters are changed, and no longer needs explicit saving of changes in server parameters.
Fixed Issues:
- Fixed a bug that prevented updating the server admin root directory
- Fixed a bug that prevented a full build after cleaning the build directory
New features:
- No longer needs saving of changes made by the admin
- Full logging of all changes made by the server admin
- No longer uses the library Html
Recommendation
- Update when convenient.
User Manual updates:
- When the server admin website must be changed it will be necessary to install the Jekyll static site generator and the Classic-Jekyll-Theme.
- The location of the sfadmin website has changed. It is no longer located in
<Project>/sfadminbut has mbeen moved to<Project>/sfadmin/_site. When accessing the serveradmin account for the first time, it will be necessary to update this location.
Open issues
- None
Anticipated changes
- Implement services and functions to allow a blogging site to accept user reactions.
No release is envisioned for these changes
Other
Link to previous release: 1.2.0
Release 1.1.0
Release 1.1.0 fixes the most annoying bugs in the earlier release:
Fixed Issues:
- 1: Domain service names table not properly initialized
- 2: Server blacklist should use serverAdminDomain blacklist
- 3: List of domains and aliases is not reconstructed correctly from file
- 4: Domain services not rebuild before starting server for first time
- 5: PHP Settings missing from domain parameters
- 6: Domain parameter phpPath is not updated correctly
New features:
- None
Recommendation: Update asap.
Release 1.0.0
Swiftfire -and all its supporting packages- have been issued in their release 1.0.0
Swiftfire has gained some functionality since the previous releases, most notably the capability to serve PHP based websites and the preparation of the split in server and domain responsibilities. I.e. server admin and domain admin. This last part is visible in the partly redesigned admin interface.
In addition it is now easier to build the project as all the necessary sources are located on github, including the compiled version of OpenSSL.
While this is very convenient to gain some quick appreciation of Swiftfire, it should be warned against using any precompiled OpenSSL binary. When you go operational using Swiftfire, you should compile your own version of OpenSSL from the original sources (be aware that some glue code is necessary)
Compiles and runs again
The app compiles and runs again, but has not been tested.
Also note that the feature set is changing.
The last stable release is 0.10.11
Intrim migration release
This release is for internal purposes only, do not use this code base, use release 0.10.11 or wait until the next release.
Bugfix release
Fixed a bug on processing a URL with a '&' in it (caused a 'hanger')
Fixed missing header logging
Upgraded (rename) SwifterJSON to VJson
Very large HTTP Request body support
In this release the serveradmin interface was improved on the code generation side of things. A.o. an HTML subproject was introduced to do the HTML code generation.
As of this release, Swiftfire now supports very large HTTP request bodies. Previously this was limited to about 32KB, now the size is nearly unlimited.
A new service was introduced to enforce completeness of HTTP requests for the traditional 'static websites'.
If websites want to make use of very large HTTP bodies, they will need to implement a service specifically for that purpose.
Completed the transition to a build-in server admin site
As of this release, the SwiftfireCore and SwifterfireConsole have been discontinued.
Swiftfire now has a build-in administration site that can be reached under "(any-domain)/serveradmin".
The id/password must be set during the initial deployment of the server.
In addition a new (sub)project 'Html' has been added to create HTML code.
Inspired by the mailing list "swift-sever-dev" (See https://swift.org/community/#mailing-lists) the next release (0.10.10) will offer support for (very) large HTTP request bodies.
Accounts and a webinterface for the Server Admin.
Support was added for (user) accounts.
A web based interface was added for the server admin.
The webinterface is not yet complete - and still a bit 'rough', but it allows a server admin to administer the Swiftfire server.
This release is a bit 'in-between' as the SwiftfireConsole is also still supported. That will be discontinued in the next release though.
When Swiftfire is started for the first time, it is mandatory to create an admin account and to specify the root location of the website that holds the 'sfadmin' pages. The 'sfadmin' website is part of the github distribution, but should probably be copied by the admin to a proper location.
To do so, start up the server and browse to 'localhost:6678'. The setup process will then automatically start.
Afterwards the server admin can always be reached by browsing to any domain and appending '/serveradmin'.