Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
funkwhale
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Zwordi
funkwhale
Commits
aee792ab
Verified
Commit
aee792ab
authored
6 years ago
by
Eliot Berriot
Browse files
Options
Downloads
Patches
Plain Diff
Fix #152: changelog and documentation
parent
ac7db737
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
changes/changelog.d/152.feature
+32
-0
32 additions, 0 deletions
changes/changelog.d/152.feature
docs/configuration.rst
+25
-0
25 additions, 0 deletions
docs/configuration.rst
with
57 additions
and
0 deletions
changes/changelog.d/152.feature
0 → 100644
+
32
−
0
View file @
aee792ab
Simpler
permission
system
(
#152)
Simpler
permission
system
=========================
Starting
from
this
release,
the
permission
system
is
much
simpler.
Up
until
now,
we
were
using
Django's
built-in
permission
system,
which
was
working,
but
also
quite
complex
to
deal
with.
The
new
implementation
relies
on
simpler
logic,
which
will
make
integration
on
the
front-end
in
upcoming
releases
faster
and
easier.
If
you
have
manually
given
permissions
to
users
on
your
instance,
you
c
an
migrate those to the new system.
On docker setups
:
.. code-block
::
shell
docker-compose
run
--rm
api
python
manage.py
script
django_permissions_to_user_permissions
--no-input
On non-docker setups
:
.. code-block
::
shell
# in your virtualenv
python
api/manage.py
script
django_permissions_to_user_permissions
--no-input
There
is
still
no
dedicated
interface
to
manage
user
permissions,
but
you
c
an
use the admin interface at ``/api/admin/users/user/`` for that purpose in
the
meantime.
This diff is collapsed.
Click to expand it.
docs/configuration.rst
+
25
−
0
View file @
aee792ab
...
...
@@ -117,3 +117,28 @@ Then, the value of :ref:`setting-MUSIC_DIRECTORY_SERVE_PATH` should be
On non-docker setup, you don't need to configure this setting.
.. note:: This path should not include any trailing slash
User permissions
----------------
Funkwhale's permission model works as follows:
- Anonymous users cannot do anything unless configured specifically
- Logged-in users can use the application, but cannot do things that affect
the whole instance
- Superusers can do anything
To make things more granular and allow some delegation of responsability,
superusers can grant specific permissions to specific users. Available
permissions are:
- **Manage instance-level settings**: users with this permission can edit instance
settings as described in :ref:`instance-settings`
- **Manage library**: users with this permission can import new music in the
instance
- **Manage library federation**: users with this permission can ask to federate with
other instances, and accept/deny federation requests from other intances
There is no dedicated interface to manage users permissions, but superusers
can login on the Django's admin at ``/api/admin/`` and grant permissions
to users at ``/api/admin/users/user/``.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment