Blog Using Laravel 5
Let's keep it as simple as possible. Configure anything you want
A full-featured blogging system for personal use. Minimum library used. No frontend theme and anything heavy or unnecessary library used.
There are four several types of users with several permissions
- Can manage articles and comments of other users
- Can manage categories
- Can manage keywords
- Can manage other users except Owner
- Can do anything that can be done by admin
- Create admin user
- Change system configuration variables
- Can write article and can manage his own article
- Can manage comments on his own article
- Can read and comment on article providing his email address.
- Can subscribe to be notified for new article
- Can search for article with
- Can navigate article based on categories
- Laravel 5.7
- VueJS 2
- Bootstrap 3
git clone https://github.com/alimranahmed/LaraBlog.giton your terminal to download this project.
- Go to the project root directory and execute
composer installto install all PHP dependencies of the project
- Create a file named as .env and copy the content of .env.example to newly created .env file
- Then execute
php artisan key:generateon your terminal/cmd to generate environment key
- Then create a Database for this project and edit the .env file to authorized this project on your database.
php artisan migrate:refresh --seedterminal on your terminal.
- Now you are ready to go, If you don't want to create any virtual host for this project then execute
php artisan server
- Now visit the url shown on your terminal, something like
localhost:8000. Its running!
Single article view
Admin panel view
Anyone is always welcome to contribute on the project. If you want to work with:
- Just create and issue(even if you want to fix the issue).
- After fixing any issue or adding any new feature just send a pull request
- I will be happy to add your code for the betterment of this project. Thanks.
If you cloned the project little bit earlier and after pulling the newer changes it's not working now, please execute the
composer update command in the CLI when you are the root directory of the project. Beside, don't forge to cross match your
.env file version with newly pulled