Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Tell the user whether the configured registry is reachable or not #1355

Closed
mssola opened this issue Jul 31, 2017 · 0 comments
Closed

Tell the user whether the configured registry is reachable or not #1355

mssola opened this issue Jul 31, 2017 · 0 comments
Labels
enhancement junior job ux
Milestone
Release 2.3

Comments

@mssola
Copy link
Collaborator

mssola commented Jul 31, 2017

In either the edit or the index page there could be a hint telling the user whether the configured registry is available or not:

  • This is useful in the index page to check whether the registry is available or not, but it's also a re-assurance when you have configured Portus with the signup_enabled option disabled, and so you configured the registry manually through the CLI.
  • In the edit page, the frontend could tell you whether the entered registry is reachable or not before actually submitting the button.

This could all be done either through a button or a link that the user has to click, or it could all be done in the frontend automatically (trying to not ping to registry too much).
@mssola mssola changed the title Tell the user whether to configured registry Tell the user whether the configured registry is reachable or not Jul 31, 2017
@mssola mssola added this to the Release 2.3 milestone Aug 2, 2017
@mssola mssola mentioned this issue Aug 9, 2017
Closed
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Aug 28, 2017
@vitoravelino
js: added some registry validation and status
6afe8bb 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
@vitoravelino vitoravelino mentioned this issue Aug 28, 2017
Merged
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Aug 29, 2017
@vitoravelino
js: added some registry validation and status
01cd402 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 10, 2017
@vitoravelino
js: added some registry validation and status
0723548 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 10, 2017
@vitoravelino
js: added some registry validation and status
8c74b1f 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 10, 2017
@vitoravelino
js: added some registry validation and status
5dc2da9 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 11, 2017
@vitoravelino
js: added some registry validation and status
bafd127 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 11, 2017
@vitoravelino
js: added some registry validation and status
93208f2 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 11, 2017
@vitoravelino
js: added some registry validation and status
5d82930 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 11, 2017
@vitoravelino
js: added some registry validation and status
38109a6 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 13, 2017
@vitoravelino
js: added some registry validation and status
278d172 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 13, 2017
@vitoravelino
js: added some registry validation and status
b28e47b 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 13, 2017
@vitoravelino
js: added some registry validation and status
1d7d6a4 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 13, 2017
@vitoravelino
js: added some registry validation and status
dc8c6d2 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Oct 13, 2017
@vitoravelino
js: added some registry validation and status
a30c270 
The registry validation was done completely on the server side. With
this, we bring some validation to the client side to antecipate and improve
the user's experience.

Also adds a hint in the registries#index pages to help the user know if the
registry that was set is reachable or not. The reachable status is cached for
30 minutes unless the user updates the registry.

Fixes SUSE#1355
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement junior job ux
Projects
None yet
Milestone
Release 2.3
Development

No branches or pull requests
1 participant
@mssola