Configuration
Input
Architecture
I'm building a really basic event registration website with an angular front end. What I'd like to do is the following:
2015.event.com 2016.event.com
All pointing to the same laravel5/angular install. What I'm curious about is where the best place is to detect/store the current year for the current user and how to deal with years that don't exist. Keeping in mind that they may quite legitimately swap from registering for the 2016 event, to viewing details of the past 2015 event.
Is this a sitter for some middleware?
Last updated
3 years ago.
For what it's worth, I've done this with "Sub-Domain Routing" - There's a pretty solid example in the documentation, which I missed :)
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast