You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2023. It is now read-only.
I'm not sure if this is an option for your right now, but I've been working on a CAS Server Laravel Package (https://github.com/loren138/cas-server) which implements a lot of the same things you have (with the exception of warn). I think your implementation has a better design pattern than mine overall also.
Anyway, I was wondering if you would have any interest in trying to merge your implementation with mine as a package such that it would be easier to distribute and have other people contribute to.
Without it being a package, adding a new feature (such as Proxy) could cause a large amount of merge conflicts if people have cloned the full laravel instance and then altered the own views/added some of their own packages.
The text was updated successfully, but these errors were encountered:
I had considered about this project should be a stand alone project or a package, finally I choose to create a stand alone project just because it's weird for a package to have an admin area.
I have just reconsidered about it, I think my project can be divided into two projects, one focuses on implement CAS protocol and be a package, another focuses on UI/admin area and be a stand alone project depends on the first one.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi Leo,
I'm not sure if this is an option for your right now, but I've been working on a CAS Server Laravel Package (https://github.com/loren138/cas-server) which implements a lot of the same things you have (with the exception of warn). I think your implementation has a better design pattern than mine overall also.
Anyway, I was wondering if you would have any interest in trying to merge your implementation with mine as a package such that it would be easier to distribute and have other people contribute to.
Without it being a package, adding a new feature (such as Proxy) could cause a large amount of merge conflicts if people have cloned the full laravel instance and then altered the own views/added some of their own packages.
The text was updated successfully, but these errors were encountered: