[major]

1. Added all the config details.
2. Incorportaed the login functionality by copying all the code from the begin-erp
project. And also added the header and footer and customised it for this project.
Added the function that will talk with the pastebin api and create the temporary paste.

As only the paste id is required for retrieving a paste, only the paste id along with the userid who
has made the post and the status of the post which will be 1 at the beginning is stored
in the posts_temp table.
Perfected the temporary insert operation
Changed from pastebin api to storing a file on the server.
The post is stored as a JSON encoded string with the fields name, content and time.

This string can be easily extended to include a lot more data.
[issue] The name of the file can't be the timestamp, as there is a possibility that
a post is submitted with the same timestamp.

[solution] TO solve this, and to introduce consistency, the post is stored with the filename
as a hash, of the userid and the present time stamp.

As the same user can never submit two blog posts in the same microsecond, and even if he/she
does, he is simply spamming or testing the system, the hash can never be the same. (A slight difference in the string being encoded completly changes the hash.)
[cleanup] Cleaned up the code, removed all the unnecessary commented code
Merge pull request #1 from icyflame/new-post

Add a new post to the blog