https://github.com/devsavage/savagedev-slim-auth-skeleton

The framework to Slim 4 projects that require an authentication system.
https://github.com/devsavage/savagedev-slim-auth-skeleton

authentication php-authentication skeleton slim-4 slim-framework slim-skeleton

Last synced: 5 days ago
JSON representation

The framework to Slim 4 projects that require an authentication system.

• Host: GitHub
• URL: https://github.com/devsavage/savagedev-slim-auth-skeleton
• Owner: devsavage
• License: mit
• Created: 2018-10-09T06:22:44.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2023-01-07T04:14:40.000Z (almost 2 years ago)
• Last Synced: 2023-08-03T00:56:15.019Z (over 1 year ago)
• Topics: authentication, php-authentication, skeleton, slim-4, slim-framework, slim-skeleton
• Language: PHP
• Homepage:
• Size: 632 KB
• Stars: 3
• Watchers: 3
• Forks: 1
• Open Issues: 10
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# SavageDev Slim Auth Skeleton

This skeleton app structures a basic authentication system for a Slim 4 application.  

*This skeleton uses the SavageDev namespace. To change this, you will need to update all the php files in the app directory as well as the command, console and middleware stubs in app/SavageDev/Console.*

## Features  

#### Authentication 

	 - Login & Register

	 - Update profile details (username, email)

	 - Update password

    View "slim-auth-skeleton-v2.sql" to see database structure

#### Console Commands

	- Make controllers

	- Make middleware

	- Make console command

    Run "php craft" in the app's directory to view more information.

#### Styling

    - Use resources/assets folder for styling and javascript files

    Utilizes webpack to style your application (default: bootstrap)	

## Installation

 1. Clone this repo to your web root

 2. Open your console and run: "composer install"

 3. To add styling support: run "npm install" or "yarn install"

 4. Import the sql file into your database

 5. Rename the .env-example file to .env and update the file to your needs, database connection, environment, url etc. (Change APP_ENV to "production" before deployment)

 7. Point to your app directory's public folder within your web configuration

 8. View website in your browser

## Help and Feedback

For any help and/or feedback, send me an email to the public e-mail shown on GitHub.