Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 506
    • Issues 506
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 28
    • Merge Requests 28
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #5601

Closed
Open
Created Apr 26, 2020 by Helmo@helmoReporter

Integrate ISPprotect version data

The ISPProtect scanner can deliver a list of CMS versions being used.

A report warning about outdated versions can be useful but why not integrate that data straight into the ISPconfig pages?

I once build a simple wrapper around https://github.com/CMS-Garden/cmsscanner.git to store it's data in my personal dashboard. Could ISPProtect do something similar? Either via the api or SQL inserts it could store it's version data in the ispconfig database. Then the sites overview page could get a CMS icon with on hover version info... maybe a background colour hinting about the status.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None