There seems to be an issue with the current HTML forms on lower resolution screens, this issue is causing the HTML input fields to expand across the entire page and breaks out of the original style of which I was trying to achieve - this then has a knock on effect as the column legend is then broken.

A re-work of the current forms should better improve the visual style and not break at any resolution.

For security reasons I feel that my installer should ideally disable the server tokens and X-Powered-By headers from being sent to the browser to improve security and accuracy of the data being sent (eg. X-Powered-By-PHP being sent with a proxy'd RoR server or J2EE application is inaccurate etc.).

This can be done by either disabling it either globally or me adding it to the code to add the disablement of the 'headers' in question being sent on a per config basis.

I'll give this some more thought before choosing a method of implementation.

When editing a rule, I found that if the origin address changes then upon saving the changes the application causes an error as it attempts to write the changes to the new file name of which does not exist.

Should implement a check to ensure that if the origin name changes that the file is renamed prior to the file being rewritten.

Need to add validation too to check that hostnames upon saving changes and saving new records don't already exist in the database.

Implementation of the RESTful API to enable third-party application connectivity to the application. - Logging here as a reminder :)

At present if Turbine is accessed via. a non-mapped host header or directly using it's IP address this shows the default Nginx landing page, ideally this should be changed to return a suitable HTTP status code or an informative message stating that a rule to handle the request has not yet been configured.

Will do some investigation into the best possible HTTP status code to use for this as a 500 or 404 in my opinion should not be the best status code(s) to use.

The static page, should be mapped to the current 'static' page folder of which is created during installation and located here: /etc/turbine/static

Currently the list of rules are visible but if the users wants to quickly browse to one of the sites there is no way at present to do that except for manaully type the address into a new browser tab/window.

I intend on adding a link so that the user can 'click' and will open the origin address in a new browser tab/window.