search

reanahub / reana-ui

REANA UI frontend
http://reana-ui.rtfd.io
MIT License
4 stars 33 forks source link

single-user deployment: 404 page not found #114

Closed tiborsimko closed 4 years ago

tiborsimko commented 4 years ago

Trying 0.7.0-alpha.1 is a single-user deployment mode:

$ reana-dev run-ci -m /var/reana:/var/reana --exclude-components=r-a-vomsproxy,r-a-krb5 -c r-d-helloworld

leads to working platform except for the home page:

$ wget --no-check-certificate https://0.0.0.0:30443
...
HTTP request sent, awaiting response... 404 Not Found
2020-08-31 09:32:49 ERROR 404: Not Found.
mvidalgarcia commented 4 years ago

With the defaults we have in values.yaml, the UI pod is not even created, that's likely the reason why you can't access it.

IIRC in the pre-kind era we had this logic inverted, UI was enabled by default and one had to pass EXCLUDE_COMPONENTS=r-ui to make deploy to exclude it.

I confirm that changing that flag to enabled works:

$ reana-dev run-ci -m /var/reana:/var/reana --exclude-components=r-a-vomsproxy,r-a-krb5 -c r-d-helloworld

...

[2020-08-31T15:37:58] reana-demo-helloworld: echo OK                                                                               │➜  reana-client git:(master)  
OK

$ wget --no-check-certificate https://0.0.0.0:30443                                
--2020-08-31 15:41:48--  https://0.0.0.0:30443/
Connecting to 0.0.0.0:30443... connected.
WARNING: cannot verify 0.0.0.0's certificate, issued by ‘CN=default-ca’:
  Unable to locally verify the issuer's authority.
    WARNING: certificate common name ‘example.com’ doesn't match requested host name ‘0.0.0.0’.
HTTP request sent, awaiting response... 200 OK
Length: 2131 (2,1K) [text/html]
Saving to: ‘index.html’

index.html                       100%[=========================================================>]   2,08K  --.-KB/s    in 0s      

2020-08-31 15:41:48 (31,8 MB/s) - ‘index.html’ saved [2131/2131]
tiborsimko commented 4 years ago

If the UX for local-user-db deployment scenarios is nice, we can enable it by default. (E.g. the person installing REANA should know which username and which password to use when logging to the UI...)

Otherwise for make vs kind, we have a possibility to store several Helm configuration options such as helm/configurations/values-dev.yaml so we could create values-dev-ui.yaml, values-dev-no-ui.yaml etc for each scenario, and based on --exclude-components option the reana-dev could use appropriate values file when bringing up the cluster.

Suggestions: