Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-server
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue 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
caosdb
Software
caosdb-server
Compare revisions
f649cd0a5d3736f26e94edd7e624464a11fbb17c to 8409cfe07ba7e34d8b94b876836ea716a932e60f
"pages/api/git@gitlab.indiscale.com:fdo/fdo-manager-webui.git" did not exist on "b003a152096b7829596b5842c5749d912690ab62"
Compare revisions
Changes are shown as if the
source
revision was being merged into the
target
revision.
Learn more about comparing revisions.
Source
caosdb/src/caosdb-server
Select target project
No results found
8409cfe07ba7e34d8b94b876836ea716a932e60f
Select Git revision
Swap
Target
caosdb/src/caosdb-server
Select target project
caosdb/src/caosdb-server
1 result
f649cd0a5d3736f26e94edd7e624464a11fbb17c
Select Git revision
Show changes
Only incoming changes from source
Include changes to target since source was created
Compare
Commits on Source (3)
MAINT: Rename master to main
· 00e3c814
Florian Spreckelsen
authored
3 years ago
00e3c814
Merge branch 'main' into dev
· 1b376387
Florian Spreckelsen
authored
3 years ago
1b376387
DOC: Changed links in documentation.
· 8409cfe0
Daniel Hornung
authored
3 years ago
8409cfe0
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
RELEASE_GUIDELINES.md
+3
-3
3 additions, 3 deletions
RELEASE_GUIDELINES.md
src/doc/Permissions.rst
+1
-1
1 addition, 1 deletion
src/doc/Permissions.rst
src/doc/conf.py
+2
-2
2 additions, 2 deletions
src/doc/conf.py
src/doc/roles.md
+2
-2
2 additions, 2 deletions
src/doc/roles.md
with
8 additions
and
8 deletions
RELEASE_GUIDELINES.md
View file @
8409cfe0
...
...
@@ -21,13 +21,13 @@ guidelines of the CaosDB Project
3.
Update the version property in
[
pom.xml
](
./pom.xml
)
(
probably
this means to
remove the
`-SNAPSHOT`
) and in
`src/doc/conf.py`
.
4.
Merge the release branch into the ma
ster
branch.
4.
Merge the release branch into the ma
in
branch.
5.
Tag the latest commit of the ma
ster
branch with
`v<VERSION>`
.
5.
Tag the latest commit of the ma
in
branch with
`v<VERSION>`
.
6.
Delete the release branch.
7.
Merge the ma
ster
branch back into the dev branch.
7.
Merge the ma
in
branch back into the dev branch.
8.
Update the version property in
[
pom.xml
](
./pom.xml
)
for the next
developlement round (with a
`-SNAPSHOT`
suffix).
This diff is collapsed.
Click to expand it.
src/doc/Permissions.rst
View file @
8409cfe0
...
...
@@ -28,7 +28,7 @@ A Permission Rule consists of:
- A type: Permission Rules can be of ``Grant`` or ``Deny`` type, either
granting or denying specific permissions.
- A `role <
manuals/general/
roles>`
__
(or user): For which users the
- A
:doc:
`role <roles>` (or user): For which users the
permission shall be granted or denied.
- A permission action: Which action shall be permitted or forbidden,
for example all retrieval, or modifications of a specific entity.
...
...
This diff is collapsed.
Click to expand it.
src/doc/conf.py
View file @
8409cfe0
...
...
@@ -55,8 +55,8 @@ templates_path = ['_templates']
# The suffix(es) of source filenames.
# You can specify multiple suffix as a list of string:
#
#
source_suffix = ['.rst', '.md']
source_suffix
=
'
.rst
'
source_suffix
=
[
'
.rst
'
,
'
.md
'
]
#
source_suffix = '.rst'
# The master toctree document.
master_doc
=
'
index
'
...
...
This diff is collapsed.
Click to expand it.
src/doc/roles.md
View file @
8409cfe0
...
...
@@ -10,7 +10,7 @@ users may have the same role, and there may be roles without any users.
The user and their roles are always returned by the server in answers to requests
and can thus be interpreted and used by clients. The most important use though
is
[
permission
](
manuals/general/
permissions
)
checking in the server: Access and
is
[
permission
](
permissions
)
checking in the server: Access and
modification of
entities can be controlled via roles, so that users of a given role are allowed
or denied certain actions. Incidentally, the permission to edit the permissions
...
...
@@ -32,4 +32,4 @@ There are some special roles, which are automatically assigned to users:
Except for the
`anonymous`
role, these special roles are not returned by the
server, but can nevertheless be used to define
[
permissions
](
manuals/general/
permissions
)
.
[
permissions
](
permissions
.rst
)
.
This diff is collapsed.
Click to expand it.