-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Runtime changes for Razor and Clam #1815
Copy link
Copy link
Closed
Labels
kind/improvementImprove an existing feature, configuration file or the documentationImprove an existing feature, configuration file or the documentationmeta/closed due to age or inactivityThis issue / PR has been closed due to inactivityThis issue / PR has been closed due to inactivitymeta/needs triageThis issue / PR needs checks and verification from maintainersThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activityThis issue / PR has become stale and will be closed if there is no further activitypriority/high
Description
Metadata
Metadata
Assignees
Labels
kind/improvementImprove an existing feature, configuration file or the documentationImprove an existing feature, configuration file or the documentationmeta/closed due to age or inactivityThis issue / PR has been closed due to inactivityThis issue / PR has been closed due to inactivitymeta/needs triageThis issue / PR needs checks and verification from maintainersThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activityThis issue / PR has become stale and will be closed if there is no further activitypriority/high
I would like some feedback concerning a use case with the razor agent.
Description
From what I understand of the razor configuration of docker-mailserver, the account/identity creation by the razor-admin is done in the Dockerfile and therefore at build time. The created identity then is the same for all instances (users) of this image. In my case the identity was created on January, 31 at 16:40.
Is this the intended way of using razor? Or should this not be done on a container/user basis?