Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A AEON Dashboard
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ARI
  • AEON Dashboard
  • Issues
  • #2
Closed
Open
Created Nov 30, 2015 by Javier Garcia Hernandez@javier.garciaMaintainer

Live demo improvement about consuming resources

We decided to identify any client using the live demo using his IP. Maybe this is no the best way of doing:

What if I use dinyamic IPs? People going to the web page once, create a subscription (queue) that maybe will not use again The service we used to detect IPs is not always working (quota exceeded, and similar things). At the end, we have rabbit full of unused queues consuming resources. We need an smart way of implementing that demo:

Using IP but deleting the subscription when you close, login, etc? We can delete all the queues created for the live demo from time to time We can identify unique users in a better way?

Assignee
Assign to
Time tracking