add custom domain

[anitanh]

fix #570 and fix #603

[ WIP ]

This PR:

• created custom domain model where subscribed user and user domain is saved
• when the user and domain are approved, it will write the user domain to server-name.txt which is included in nginx so the domain will be included in the allowed hosts.

@timlinux and @cchristelis is this the right approach?

in the admin panel:

[timlinux]

I think we should just call it 'Domain' and then create a Domain entry for e.g. http://projecta.kartoza.com which is the default domain that all new projects get added to that do not have an explicitly set domain. Then add a foreign key reference to Domain from both the organisation and project models.

[timlinux]

I would imaging that since we will on a dedicated server using * for server name might be a simpler approach and then let projecta handle whether the hostname in the header of the request if valid or not.

[timlinux]

(that we we do not need to use server-name.txt tricks)

[timlinux]

I think the domain would need to be independently unique - otherwise what will happen if two users try to register the same domain?

[timlinux]

lets order by the domain name

[timlinux]

@Ann26 Referring back to my original ticket at #635 I think it makes more sense to make an atomic PR that adds an organisation model and associates each project with each organisation. By default we can associate projects with the 'global' organisation until the are assigned to a specific organisation.

Then each organisation and project will get associated with a domain.

[timlinux]

@Ann26 can you also take a look at this PR from @meomancer and review whether the code will fit within the framework we are setting up here:

#361

[anitanh]

ok @timlinux will do

[anitanh]

Hi @timlinux , looking at @meomancer 's PR (#361) I think the code can fit our framework with a bit of modification.

I tried it in my local and using it we can assign additional administrators that can have permissions the same as the owner in the project, as shown below: (for staff users, they get all projects)

So in above example case, I am (not a staff) the owner of Inasafe project and an administrator of XProject project. I have the same permissions as the owner of XProject eventhough I am not the owner of it.

The app also includes custom template tag that we can implement in template, e.g. the_project|is_project_administrator:user

Maybe the Project Collaborators can be the Managers of each app (e.g. changelog, sponsorship, certification) ?

In conclusion,

• I think using permission app, we can manage permissions separately from the project model
• Its custom template tag can simplify the template code when dealing with permissions (which user see which blocks).

[anitanh]

Hi @timlinux , here is update:

• Added organisation model
• Added organisation create and list view
• The existing projects are assigned to default organisation (Kartoza)
• Added domain model
• Added domain create and list view
• Domain list view only available for staff
• Added domain check middleware
• Changed nginx conf server name to * (wildcard)
• When a domain is registered with role as project, the site will point to project page
• When a domain is registered with role as organisation, the site will point to home page (project list page) with only showing the project in that organisation.
• Added domain check middleware test
• Update existing tests

Gifs:

• Organisation create view
  

• Organisation list and pending view
  

• Domain create view
  User may click on register a domain from navigation.
  

Or may click on set up custom domain button on project page

• When domain is not registered or not approved yet
  

• Domain list view (only available to staff users)
  

• Domain as organisation role
  

• Domain as project role
  

Travis is still failing, I am still investigating it.

[timlinux]

Wow @Ann26 beautiful work! Please merge when you have travis passing and then deploy it to staging so I can play with it a bit.