Homestead and Subdomains

@macmotp have you add subdomain.site.app in your hosts file?

Depends at what level you want to manage the domains but I think you want different routes depending on if it's subdomain or not?

Laravel routes are also able to handle wildcard sub-domains, and will pass your wildcard parameters from the domain:

Registering Sub-Domain Routes

Route::group(array('domain' => '{account}.myapp.com'), function()
{

    Route::get('user/{id}', function($account, $id)
    {
        //
    });

});

Ref: http://laravel.com/docs/4.2/routing#sub-domain-routing

Thank you @faisal_arbain and @bashy for your reply. When I submit the question I forgot to mention that I had already added the subdomain in the hosts file and used the sub-domain routing. My problem was related to an incorrect configuration of Homestead. Here is the solution:

1) add all the subdomains you need on /etc/hosts:

127.0.0.1 site.app
127.0.0.1 subdomain.site.app

2) map all the subdomains in the file Homestead.yaml pointing to the same root (this was the issue because I needed to run "vagrant provision" and not just "vagrant up"):

sites:
    - map: site.app
      to: /home/vagrant/site/public
    - map: subdomain.site.app
      to: /home/vagrant/site/public

3) use sub-domain routing in Laravel as follow:

$router->group(array('domain' => 'site.app'), function()
{
    get('/', function() {
        return 'main app!';
    });
});

$router->group(array('domain' => 'subdomain.site.app'), function()
{
    get('/', function() {
        return 'subdomain app!';
    });
});

Oh right, always best to explain what you've done already :)

Glad you got it sorted!

Out of interest does anyone know how to get this working with wildcard subdomains for Homestead?

@joshuahornby have you tried watching this https://laracasts.com/lessons/wildcard-subdomains

@dberry Yes, this isn't for homestead.

What do you want to allow? Pick up all subdomains in Nginx?

http://nginx.org/en/docs/http/server_names.html for nginx... you'll still have to add the hostnames to your /etc/hosts.

I ended up following this http://passingcuriosity.com/2013/dnsmasq-dev-osx/ and then using Nginx

@joshuahornby Do you mind elaborating on how you got this to work? I have tried quite a few things and cannot get this to work.

I have confirmed DNSmasq is working. I installed through homebrew. I also altered the serve.sh file in Homebrew to include a wildcard in front of the server_name and I still cannot get anything to work.

@ross.edman Sure, after setting up DNSMasq I homestead ssh and then edited /etc/nginx/sites-available/mydomain" and added the wildcard before the domain in there, so I have something like

server_name  example.org  *.example.org;

Then I just restarted homestead.

@joshuahornby Thanks a lot. I have had some other problems with this, but I will try this.

@joshuahornby When I restart Homestead with provisioning it gets overridden :S

EDIT: Nevermind I have figured it out

Just did this. Here's my configuration:

On homestead vagrant box (to access: homestead ssh)

• sudo vim /etc/nginx/sites-available/homestead.app: server_name homestead.app *.homestead.app;

On Mac:

• sudo vim /etc/hosts: 192.168.10.10 homestead.app
• sudo vim /usr/local/etc/dnsmasq.conf: 'address=/app/192.168.10.10'
• sudo vim /etc/resolver/app: nameserver 127.0.0.1

Anyone got this working with Ubuntu? All info I find seems to be for OS X and I just can't get it to work.

Anyone for for Ubuntu ?

I simply added the following to my site declarations in sites.yaml

• map: '*.mysite.dev' to: /mycode/on/vagrant

single quotes worked. I also use dnsmasq for all .dev domains to point to the homestead IP.

the solution of @domandtom worked for me, if you have an other subdomain not working on windows with homestead/vagrant: log into your vagrant (vagrant ssh)

cd /etc/nginx/sites-available/
ls

here are the files to edit for your domains, look up your domain, for example devdomain.dev, and then edit that one:

sudo vim devdomain.dev

look for the line where your domain is, in this example devdomain.dev:

server_name devdomain.dev;

and add the * domain to the same row like this:

server_name devdomain.dev *.devdomain.dev;

ait: thought it worked, but still didn't managed to get api. been handled by the passport token verivication the right way. we're changing it back to /api again, but if someone wants other subdomains working in homestad/vagrant on windows, you can use the info above.

Bart

@joshuahornby I think this should be the accepted answer, thanks alot

@domandtom Dude you just saved my day. Spent almost a trying to configure wildcard subdomain on my homestead. "sudo vim /etc/resolver/app: nameserver 127.0.0.1" was the saviour.

Kudos (Y)