kickthemooon's avatar

Is this something I can share on GitHub?

So I made my first repository on GitHub. It is a "Laravel base app" with user access management, user email verification and admin panel. It uses Zizaco/entrust plus the permissions have an additional field/property, "route" and authorize middleware. So users get a 403 permission denied if their role doesn't have the permission to access a certain route.

Visit https://github.com/kickthemooon/LaravelBaseApp

I wanted to ask if this is ok as a repository to share and have on GitHub?

0 likes
6 replies
EmilMoe's avatar

You can do as according to https://opensource.org/licenses/MIT so basically yes, if you don't try to take credit for more than what you did and leave credits for others.

Besides that you shouldn't include vendors, etc in your repos

And btw make your stuff as a package and don't include any Laravel at all :-)

kickthemooon's avatar

@EmilMoe All the credits are there, I didn't change anything that I was supposed to change.

Now about the vendors, I noticed that it shouldn't be included but how will someone get the vendor folder when they try to set it up on their end?

Sorry never did this before thats why im posting it here...

bashy's avatar

Ignore the /vendor folder in .gitignore file and then do

git rm -r vendor

They can do this to install the files

composer install
kickthemooon's avatar

@bashy so composer install will get them the vendor folder?

Ok thanks a lot. I'll update it the way you suggested.

EmilMoe's avatar

Yes exactly. Do the same with the output of your gulp file and the node_modules folder if they happen to be there.

jlrdw's avatar

Looks good, I'm still using version 5.1 but may give this a go on a 5.2 later on.

Please or to participate in this conversation.