I stumbled on your tuts yesterday and in a few short hours learned more than I knew about Laravel since picking it up last month. Thank you, you have a good way of teaching.
So I started out with your tut on https://blog.pusher.com/laravel-subdomain-routing/ happy as a pig in mud then found your tut on multiple-auth which in combination provide the structure I am looking for...where I can provide a single app and have a subdomain for say developers. and admin. and support. and client. and isolate each user in their context (developer, admin...). All this pulling from the same database that shares most of its data among all user types.
So I implemented them both. Created view folders for each context where admin and developer and support all have different landing page. I would like to share the login and registration among other common àges throughout the app. Problem I am working through is as you probably figured by now is that the mutli-auth uses path site.com/register/admin where the subdomain needs to use admin.site.com/register.
I am seeing if I can work this out now but thought I would shout out to see if you were interested in providing a little direction or even a quick tut on how to combine your two tuts into a "multi-subdomain authenticated app"
I stumbled on your tuts yesterday and in a few short hours learned more than I knew about Laravel since picking it up last month. Thank you, you have a good way of teaching.
So I started out with your tut on https://blog.pusher.com/laravel-subdomain-routing/ happy as a pig in mud then found your tut on multiple-auth which in combination provide the structure I am looking for...where I can provide a single app and have a subdomain for say developers. and admin. and support. and client. and isolate each user in their context (developer, admin...). All this pulling from the same database that shares most of its data among all user types.
So I implemented them both. Created view folders for each context where admin and developer and support all have different landing page. I would like to share the login and registration among other common àges throughout the app. Problem I am working through is as you probably figured by now is that the mutli-auth uses path
site.com/register/adminwhere the subdomain needs to useadmin.site.com/register.I am seeing if I can work this out now but thought I would shout out to see if you were interested in providing a little direction or even a quick tut on how to combine your two tuts into a "multi-subdomain authenticated app"
Regards