Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #515
Closed
Open
Issue created Jan 09, 2019 by André Anjos@andre.anjos💬Owner

BEAT website certificate and expiration

The BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).

To avoid a pressing issue then, and leave time for people to "adapt" to a new address, I propose we start looking for solutions now.

@samuel.gaist: Could you please contact the system group (via a ticket) and ask them which solutions could be setup to host the platform under "idiap.ch".

I thought of 2 options, but I'm not sure whether these are feasible:

  1. "https://beat.idiap.ch": The advantage is that swagger docs would start working again...
  2. "https://www.idiap.ch/software/beat/platform": This would be the one that makes more sense "structurally"
Assignee
Assign to
Time tracking