Tutorial-First-Application
phpframework
Tutorial-First-Application | phpframework | |
---|---|---|
12 | 3 | |
125 | 4 | |
0.0% | - | |
0.0 | 10.0 | |
over 1 year ago | over 1 year ago | |
PHP | PHP | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Tutorial-First-Application
-
Weekly help thread
b) Separate out all SQL and PHP database code. Put these in separate classes similar to this example Slim First Application Mapper class. You can decide later if you want to use a framework's DB code or not - it would be simply refactoring your existing code and not changing (hopefully) the API that you started using internally
- Any good no framework PHP MYSQL web app in github, I can learn from?
- Simplest PHP template ever. Password hashed PDO register and login. Just add Postgres DB info in .ini file or change the Singleton class for MySQL. User table should have "username" and "password" fields. Plus whatever else you want. simple_dom_html.php library included. PHP 7.4+
-
Is a framework necessary to create a PHP project?
Yes, as an example, the First Application's business logic (not that it's much) doesn't tie itself to the framework, as one example. Odan's Slim Skeleton, ADR Example (yes, I know you are the author), and the Aura Payload example class can be seen as other examples.
-
Do I need Laravel for an HTTP API project? If so, why?
Both. Build business logic with PHP, then use a framework for the common functionality (routing, auth, validation, etc). Look at Slim's First Application to show a very simple example of this - https://github.com/slimphp/Tutorial-First-Application
- How to move up to PHP 8 and Object Orientation?
- advice for modernizing a legacy web app
-
I'm new to PHP OOP and looking for feedback on my proposed OOP design structure before I dive in a start coding it. Thanks!
Another option, to me and speaking to the OP as an alternative, it is simpler to add some Data Mappers/Repositories to abstract away the Database code. Good examples is the sample ADR application, Payload library example, Slim 3 First Application, or this Slim 4 Skeleton application
-
Storing DB credentials
Yes, you can. Did you look at the example I provided? Want another one? Slim Framework's first application does exactly this:
-
Help with making my MVC "Framework"
https://github.com/slimphp/Tutorial-First-Application <- Uses the Slim framework
phpframework
-
Is a framework necessary to create a PHP project?
Here is the finished code: https://github.com/cipher-code/phpframework
- Show HN: A DIY PHP Framework
What are some alternatives?
React - Event-driven, non-blocking I/O with PHP.
adr-example - An example ADR subsystem.
PHP Dotenv - Loads environment variables from `.env` to `getenv()`, `$_ENV` and `$_SERVER` automagically.
Slim - Slim Framework 4 Skeleton Application
slim4-skeleton - A Slim 4 Skeleton
php-app - Barebones PHP app with PDO Singleton setup for Postgres. Register, Login, Index page. Simple cache and simple_html_dom library included. Add your own DB info.
phroute - A super fast PHP router, with route parameters, restful controllers, filters and reverse routing.
no-framework-tutorial - A small tutorial to show how to create a PHP application without a framework.
skeleton - Standard PHP package skeleton.
framework - PHP Framework providing ActiveRecord models and out of the box CRUD controllers with versioning and ORM support
ticketsapi - just a rest api done with slim v4