subdomain naming

pete's Avatar


12 Dec, 2008 08:40 PM

I'm new to Lighthouse, and I'd like to set up an account for a client project that we're working on at Unspace; call it QuoteSys.

Of course, we have many projects and might want to migrate other projects to Lighthouse as well.

So, do I call my subdomain unspace or quotesys?

This might be a completely dense question, but I see people expressing confusion in the forums about the same issues. I did look around and I found this issue:

However, it doesn't really tie things together for me. For example, I'm doing this on behalf of a client, but what if they stop working with us, or us them? Plus, my client would likely look at an unspace subdomain and get uptight about another company "owning" their internal ticketing system.

I won't put up a fuss, I just need to understand what someone in my role is intended to do in an optimal use case scenario.

  1. 1 Posted by Rick on 12 Dec, 2008 10:12 PM

    Rick's Avatar

    It's all up to you. Our clients usually prefer to have their own Lighthouse subdomain. This also means you're not necessarily footing the bill for a massive account, and the client's ticket data is not tied to your company.

    If you do decide to host the tickets on your company account, it's a simple matter for us to migrate them to another account if needed. Very soon we'll have some api hooks so anyone can setup their own ticket migrations across accounts or projects.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac