Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
F
foodsharing
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 218
    • Issues 218
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 25
    • Merge requests 25
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • foodsharing-dev
  • foodsharing
  • Issues
  • #1070

Closed
Open
Created Mar 30, 2021 by chandi@alangeckerOwner

On Deployment, chatserver should be restarted

What is the current bug behavior?

When a new release is published, the chatserver still runs on the old release.

What is the expected correct behavior?

The chatserver should be restarted, so that the new code is applied.

Possible fixes

maybe set a flag file like chatserver_needs_restart and a cronjob running as root which checks for that file and calling systemctl restart fs-chatserver, in case of this file existing?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking