This repository was archived by the owner on Sep 9, 2025. It is now read-only.
user accounting #285
Open
user accounting #285
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature/image registry yaml
Fix/bug fixes v2.1.2
2.2 ui updates
The tabs for nightly and remote should be loaded only when accessed
This reverts commit d8e06c1.
Fix `--username` not being required
removed the hard coded jwt secret key
fixed config set because of missing save statement
Extra container details on main page
Linux PAM authentication
Enable limits.cpu setting on container creation menu
Fixed bug on container update while validating
Update versions of libraries
Adds exact version 2.1.2 for Werkzeug.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
please add features to manage users and user access to resources
example : user1 can create , delete and 2 snapshot ... container but only access to 1 gig ram and cpu 20% of host
user1 should not access to network .. profile and storage pools
user1 should only manage his containers not other user containers
and something like that ...
thanks ...