White Label a System

Anyone have any suggestions would building an API be the best option?

I'm just on my way out, I'll be around on Sunday if someone else hasn't chimed in until then.

Cheers @mstnorris

Why not sub domain routing and client CNAME their domains?

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

Route::group(['domain' => '{account}.myapp.com'], function()
{
    // account specific route group        
});

Like Wordpress.com does for blogs: example.com mapped to: example.wordpress.com

Here is a Laracasts lesson - Wildcard Subdomains

@BrianDillingham no this is not how the client wants to do this, but good idea though and already had discussions with them about it.

@mstnorris your input?

@lstables sorry for not getting back to you sooner. Missus's birthday.

What else has the client specified?

@mstnorris haha no worries....Hope it was a good un :)

Just wanting to white label the system, so i'm thinking build an API that would communicate with the system already built then carbon copy it as a central place where all the white labellers would use it and be able to use on there own domain(s) and servers etc.

Basically to sell it on but the client would still be able to push new features to it and gain a monthly income stream from it.

I hope this makes sense :)

Yes, that makes a lot more sense but I am sorry that I can't give you any real input on this one. It isn't something I am too familiar with so it wouldn't be appropriate for me to comment.

I'd love to be kept up to date though with your progress and the decisions you make as it'd be cool to learn something new.

Yeah I'll update you think I'll go down the road of building an Api that way I get to play with lumen t the same time lol.

Any news on that? I want to build a white label solution myself and I'm looking for best practices for the architecture.

No the project never materialised, sorry! if anyone else has thoughts on this then do share.