Actions
Feature #9837
closedAllow at least for development purposes using an existing user instead of klever
Status:
Rejected
Priority:
Urgent
Assignee:
-
Category:
Deployment
Target version:
-
Start date:
09/25/2019
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
Currently the Klever deployment script creates 'klever' user to run controller and scheduler. Though there is an option for development working directories are managed by a different user at debugging. This is inconvenient. Lets implement an option to use an existing user for development deployment to avoid extra management with rights.
Updated by Evgeny Novikov about 4 years ago
- Status changed from New to Rejected
I do not understand the issue from its current description. If you are still interested in it, please, describe it properly.
Actions