Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ui: optional announcement #83

Closed
mvidalgarcia opened this issue Feb 28, 2020 · 2 comments · Fixed by #101, reanahub/reana-server#254 or reanahub/reana#328
Closed

ui: optional announcement #83

mvidalgarcia opened this issue Feb 28, 2020 · 2 comments · Fixed by #101, reanahub/reana-server#254 or reanahub/reana#328

Comments

@mvidalgarcia
Copy link
Member

This can be useful for reana-dev and reana-qa instances or in case we want to announce e.g. an intervention with expected downtime.

Quick draft idea:

image

@tiborsimko
Copy link
Member

Also, on QA, we could display some permanent warning text there:

(!) Please note you are using REANA QA developer preview site. If you are looking for REANA production site, please go to _reana.cern.ch_.

@mvidalgarcia
Copy link
Member Author

I was wondering what is the most effective way of implementing this. Some ideas:

  • a) Easier way: Just a simple key in config.js that prints its content if exists. Probably not ideal in terms of enabling the announcement on-demand as it'd require rebuilding the image.
  • b) Harder way: And env var on r-server whose content is sent when user is loaded (/api/me) and email, token, etc. are saved in the redux state.

I invite you to share some other ideas you might have or express your preferences.

@mvidalgarcia mvidalgarcia self-assigned this Jun 2, 2020
mvidalgarcia added a commit to mvidalgarcia/reana-ui that referenced this issue Jun 2, 2020
mvidalgarcia added a commit to mvidalgarcia/reana that referenced this issue Jun 3, 2020
mvidalgarcia added a commit to mvidalgarcia/reana that referenced this issue Jun 4, 2020
mvidalgarcia added a commit to mvidalgarcia/reana-ui that referenced this issue Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment