Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E ef-gui
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vfos
  • ef-gui
  • Issues
  • #17

Closed
Open
Created May 09, 2019 by dll@dllOwner

Refactor UI with enabler users in mind

We built the UI around the use case of an actor that inserts enablers, versions and instances. We didn't gave much thought to those that use enablers.

A striking example is the way that an instance information is displayed, specially for those there were automatically installed. We show the internal URL and port, which are useless on this case.

We should rather add a column to show the exposed URL, the one that can be accessed through request-handler, and perhaps hide the URL and port whenever an enabler was auto installed.

We should also add links to the request-handler documentation and lib-access-enabler-js . And take a further look at this from the viewpoint of someone using enablers withing a vApp

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking