pfc001 Not enough information

Second Assessment – Laravel Project

Develop a Laravel web application and host it on a public web server (hence module starts with AWS

Ubuntu LAMP setup). I/we need to be able to access your Laravel web application for a demo so it needs to  be public but possibly protected. It does not necessarily need to run 24/7 continuously.

The theme and content of the site is for you to decide, but they must be approved by your Lecturer as being of sufficient complexity for an Honours module. Set up a blog using your own web space (e.g. AWS,Raspberry Pi) or a free service (e.g.Blogger.com or Wordpress.com) and use it to record your progress with this part of your module, including screen captures and video captures of work in progress. You should record any difficulties you encountered, and how you overcame them.

The blog content should be entirely specific to the Laravel work you havem attempted/completed. Use blog posts to document your achievements, the problems you encounter and the solutions you develop as you progress. Don’t leave this to a few posts at the last minute. It is your responsibility to use the blog posts to highlight your technical achievements so that I do not miss anything important when I assess your work.

Marks will be allocated for technical aspects up to 30%, and for content (including your blog) up to 30% giving a total of up to 60% of the overall marks for the module.

These instructions are issued in advance but after more Laravel material has been covered a detailed discussion/guidance session will take place in a lecture.

Submission deadline (pdf to Aula) is 2355 Sunday 3th December with your work to be demonstrated in the week of 4th-8th December. You will have other deadlines. It is essential to start on the Laravel assignment no later than late November

Format of submission

1. The Aula submission (see deadline above) is a single side of A4 submitted as a pdf file giving essential details such as your name, Banner ID, URL of Laravel project, URL of your blog and any usernames/passwords I or the external examiner might need to access or assess your work. You must include a URL for phpMyAdmin and a MySQL username/password to allow inspection of your database or databases.

2. Demonstration (see dates above) of your Laravel work. I suggest you host your Laravel project behind http authentication (you may need Distributed Access Control) to prevent somebody using it to upload/share illegal material that you would be held responsible for. Backups are your responsibility.

3. The blog reporting on your Laravel work must be on a public web server available 24/7 continuously for marking. Don’t use your Laravel application to host your blog even if your Laravel application is a blog or CMS application. This blog is marked for content only. The blog has no functionality that is

assessed. Alternatively, you can just submit your blog as a pdf instead of hosting it in a public web server.

Your work will be penalised if you publish information (eg account details, API keys etc) insecurely on your Laravel or blog!