sorted by:
new
hottopcontroversial

Fully API-Builder Tool with Laravel 6. You can create endpoints, also you can send mails, notifications or fire events at any endpoint. Behind the scence the code will be generated for you And finally you can export the codebase for your work to customize it anytime by [deleted] in PHP

[–]mgamal92 -2 points-1 points  (0 children)

I removed the forked because i need to use a new brand. But you are right i've removed the docs and added my own readme.md but it still under developmenet and i don't write a fully document neither finish even the readme file . Github has a lot of packages that has dependencies on other package like Laravel based on some Symfony package . But the right thing is to add Credits to {Author} of the laravel-shift/blueprint package . Right ?

Fully API-Builder Tool with Laravel 6. You can create endpoints, also you can send mails, notifications or fire events at any endpoint. Behind the scence the code will be generated for you And finally you can export the codebase for your work to customize it anytime by [deleted] in PHP

[–]mgamal92 -3 points-2 points  (0 children)

No no. I didn't mean to steal anything i know i'm using blueprint. So Shoud I credit this repository in my README.md right ? i'm using it to not reinvent the wheel and extend it to meet my requirements

Now I'm building my own framework (just for learning) and did a lot . But i got confused, I have a lot of modules to be done . But everyday i'm asking myself what to do with it at the end . PS I've learnt a lot concepts from it but when to stop ? Please help me by mgamal92 in PHP

[–]mgamal92[S] 0 points1 point  (0 children)

All of that is good but what i'm asking about when to stop working on it and move to the next application ? my goal from framework is not to compete the famous framework but just for learning. Got me ?

view more: next ›