Make also available for other customers

[lexvand]

The Parramatta dashboards can potentially also be sold to other customers in Australia.

Therefore we need a demo for these customers or a time-estimation what such a demo would cost.

The current dashboard of Parramatta is found at:
parramatta.lizard.net/floodsmart

This parramatta dashboard app should also be available for some other customers that need their own url and client configuration.

For example (fictional):
canberra.lizard.net/floodsmart shows the alarms rain and scenarios configured for Canberra.

A list of all urls/companies for which it should work will follow.

Technical details:

The requirements already work.

• The title of the dashboard can be configured like this in the client config:

{
"dashboardTitle": "FloodSmart Parramatta Dashboard (configured title)",
"showTermsAndConditions":true,

See:

https://nxt3.staging.lizard.net/admin/lizard_nxt/clientconfiguration/4/change/

https://nxt3.staging.lizard.net/floodsmart/

• The url for the dashboard already works

Here is the url:

https://demo.lizard.net/floodsmart/

Here is the configuration:

https://demo.lizard.net/admin/lizard_nxt/clientconfiguration/55/change/

The second tile is now called “ Measurement stations2” to prove that this is really the above configuration.

Be aware that the “client slug” in the configuration record currently has to be called “parramatta-dashboard” for the dashboard to work. This isnot visible for the customer. Estimation to change this 0.5 points / days.

Alternatively yu can change the “client_slug” name to and then use the url

https://demo.lizard.net/floodsmart/

[FRNT-564] created by tom.deboer

[lexvand]

Joeri Verheijden

Hi Joeri,

Here is the ticket

Lex van Dolderen

Lex, can we pick this up asap? When?

by 5b3b278169812b2ef3f78d91

[lexvand]

Remco Gerlich

Hi Remco,

I like to hear your opinion on this.

What would be the ideal approach?

Maybe it is already working btw because I see nothing in nginx that is hardcoded to parramatta in the base url.

by 5b3b278169812b2ef3f78d91

[lexvand]

Joeri Verheijden

Hi Joeri

It seems to be working already.

Here is the url:

https://demo.lizard.net/floodsmart/

Here is the configuration:

https://demo.lizard.net/admin/lizard_nxt/clientconfiguration/55/change/

The second tile is now called “ Measurement stations2” to prove that this is really the above configuration.

Possible improvements

The title is not configurable yet, so now is is always called “FloodSmart Parramatta Dashboard”. Estimation for making this configurable: 0.5 points / days.

Be aware that the “client slug” in the configuration record currently has to be called “parramatta-dashboard” for the dashboard to work. This is probably not a problem for the demo. Estimation to change this 0.5 points / days.

Please let me know what the next steps should be and with which priority.

kr Tom

by 5b3b278169812b2ef3f78d91

[lexvand]

Joeri Verheijden

Currently I can also use the Parramatta app to open a non-parramatta dashboard:

https://demo.lizard.net/floodsmart/dashboard/

this opens the dashboard at:

https://demo.lizard.net/dashboard/

This means that for demo purposes we could hang the Demo dashboards under demo.lizard.net/floodsmart/some_dashboard_name

Would this be enough for the demo?

If we would however need a different portal name like

some_customer_name.lizard.net/floodsmart this may require some haproxy configuration.

I need to ask Reinout

by 5b3b278169812b2ef3f78d91

[lexvand]

Reinout Rees, van Hi Reinout,

If I like to have

.lizard.net/floodsmart to go to the parramatta dashboards

Will this require HAproxy config changes ?

We have up to 8 potential customers that like a demo.

If this costs a lot of work I could also ask if I can just use demo.lizard.net untill they really show some money.

kr Tom

by 5b3b278169812b2ef3f78d91

[lexvand]

Joeri Verheijden

Hi Joeri,

I spoke to Reinout and normally we create the domain after the user is customer.

This means that for the demo’s they can use

demo.lizard.net/floodsmart/

• Would this be good?
  • → No we need those dashboards right away on the correct url for the customers. They will get the dashboards for one year.
    • Ask Reinout for HAproxy
    • Ask Joeri for specific urls
    • Talk to Remco concerning performance

As soon as they become a customer they could use the domain:

https://.lizard.net/floodsmart//

• If you prefer another url postfix (other then floodsmart) then this would require some extra work. 0.5 day. If the “floodsmart” url is good then this cost no extra work. Configuring the title would then be the only extra dev work (0.5 day).
  • → The postfix floodsmart is good. We could always change this later.

I can start as soon as you let me know what you decide about above bullets.

kr Tom

by 5b3b278169812b2ef3f78d91

[lexvand]

Joeri Verheijden

Hi Joeri,

Turns out all requirements are already working.

See also “Technical details:” under description.

For it to work we now need to:

• configure the portal domains in lizard/admin
  • Consultants could do this
• configure the portal urls in HAproxy
  • Reinout could do this if he knows the urls.

I will assign this ticket to you.

kr Tom

by 5b3b278169812b2ef3f78d91

[lexvand]

Does this still need work to make the title configurable? Other than that it should just work.

by remco.gerlich

[lexvand]

Made a separate issue for the configurable title. https://nelen-schuurmans.atlassian.net/browse/GH-574

by lex.vandolderen