Recruitment website

In my previous post I talked about an ASP.NET website created in the Azure cloud. I have a design document with many more features to add with time permitting. Already, there is Google OAuth authentication for creating accounts but additional ideas/features include integration with an API, such as indeed.com. This is from memory, I need to deploy the project again like a year ago to test and see what needs done. One of the main points was to make it prettier. My focus was on I.T. jobs, so a noted improvement was to add graphics that would attract techie users. Importance was placed on the homepage, to give a good first impression, considering the impact it has on visitors continuing to use the application. I hope to get my cloud hat back on soon and will be sure to post a link to the hosted app.

Website statistics

Website stats are important for web admins.
Some of the main features include:

  • Page hits
  • Geographical location of the page hits
  • Number of unique visitors
  • Entry to and Exit from pages
  • Time spent on pages
  • Error pages
  • Bandwidth usage

For this task I have chosen the very well known Awstats log file analyser as it is free. I have seen that free WordPress plugins can also offer web stats but will have yet to try them out.  Installing Awstats on Linux is ten times easier than Windows, of which directions for both are widely available through your preferred search engine.

Finally, you may want to restrict your awstats directory to the localhost and your remote IP. Accessing the webpage through an IP other than your server (a static IP), will likely be dynamic, so will be a pain to update. A solution to this would be to register with a Dynamic DNS service (such as no-ip.com) and input the account details to a supported broadband router. The DNS host name that you choose can then be added to the Apache configuration rules for the awstats directory to restrict to this host, for example “Require forward-dns yourhostname.ddns.net”. A little explanation on this rule is that normally the host rule will do a reverse lookup, whereas forward-dns will verify the forward resolution of the domain.