Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
05ca6c39
Commit
05ca6c39
authored
Sep 03, 2020
by
Amy Troschinetz
Committed by
Marcia Ramos
Sep 03, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs: correct the numbering in a numbered list
parent
2405d955
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
44 additions
and
44 deletions
+44
-44
doc/development/application_limits.md
doc/development/application_limits.md
+44
-44
No files found.
doc/development/application_limits.md
View file @
05ca6c39
...
...
@@ -17,50 +17,50 @@ limits](https://about.gitlab.com/handbook/product/product-processes/#introducing
### Insert database plan limits
In the
`plan_limits`
table,
you have to create a new column and insert the
limit values. It's recommended to create
separate migration script files.
1.
Add
new column to the
`plan_limits`
table with non-null default value
that
represents desired limit, such as:
```
ruby
add_column
(
:plan_limits
,
:project_hooks
,
:integer
,
default:
100
,
null:
false
)
```
NOTE:
**Note:**
Plan limits entries set to
`0`
mean that limits are not
enabled. You should
use this setting only in special and documented circumstances.
1.
(Optionally) Create the database migration that fine-tunes each level with
a
desired limit using
`create_or_update_plan_limit`
migration helper, such as:
```
ruby
class
InsertProjectHooksPlanLimits
<
ActiveRecord
::
Migration
[
5.2
]
include
Gitlab
::
Database
::
MigrationHelpers
DOWNTIME
=
false
def
up
create_or_update_plan_limit
(
'project_hooks'
,
'default'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'free'
,
10
)
create_or_update_plan_limit
(
'project_hooks'
,
'bronze'
,
20
)
create_or_update_plan_limit
(
'project_hooks'
,
'silver'
,
30
)
create_or_update_plan_limit
(
'project_hooks'
,
'gold'
,
100
)
end
def
down
create_or_update_plan_limit
(
'project_hooks'
,
'default'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'free'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'bronze'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'silver'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'gold'
,
0
)
end
end
```
NOTE:
**Note:**
Some plans exist only on GitLab.com. This will be no-op
for plans
that do not exist.
In the
`plan_limits`
table,
create a new column and insert the limit values.
It's recommended to create two
separate migration script files.
1.
Add
a new column to the
`plan_limits`
table with non-null default value that
represents desired limit, such as:
```
ruby
add_column
(
:plan_limits
,
:project_hooks
,
:integer
,
default:
100
,
null:
false
)
```
NOTE:
**Note:**
Plan limits entries set to
`0`
mean that limits are not enabled. You should
use this setting only in special and documented circumstances.
1.
(Optionally) Create the database migration that fine-tunes each level with
a
desired limit using
`create_or_update_plan_limit`
migration helper, such as:
```
ruby
class
InsertProjectHooksPlanLimits
<
ActiveRecord
::
Migration
[
5.2
]
include
Gitlab
::
Database
::
MigrationHelpers
DOWNTIME
=
false
def
up
create_or_update_plan_limit
(
'project_hooks'
,
'default'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'free'
,
10
)
create_or_update_plan_limit
(
'project_hooks'
,
'bronze'
,
20
)
create_or_update_plan_limit
(
'project_hooks'
,
'silver'
,
30
)
create_or_update_plan_limit
(
'project_hooks'
,
'gold'
,
100
)
end
def
down
create_or_update_plan_limit
(
'project_hooks'
,
'default'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'free'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'bronze'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'silver'
,
0
)
create_or_update_plan_limit
(
'project_hooks'
,
'gold'
,
0
)
end
end
```
NOTE:
**Note:**
Some plans exist only on GitLab.com. This will be a no-op for plans
that do not exist.
### Plan limits validation
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment