Project

General

Profile

RusRedmineSettings » History » Version 5

Ruslan Khasanov, 2013-03-16 20:36

1 1 Denis Savitskiy
[[RusGuide|Руководство]]->[[RusAdministrator_Guide|Руководство администратора]]
2
3 5 Ruslan Khasanov
Оригинал: [[RedmineSettings|Application settings v.29]]
4
5 1 Denis Savitskiy
{{>TOC}}
6
7
h2. Основные настройки
8
9
h3. Название приложения
10
11 5 Ruslan Khasanov
Название, которое отображается в заголовке приложения. Это ссылка под полоской с « Домашняя страница/Моя страница/Проекты/Помощь», которая отображается, когда вы вошли в систему.
12 1 Denis Savitskiy
13
h3. Текст приветствия
14
15 5 Ruslan Khasanov
Текст отображаемый на домашней странице Redmine. Текст может содержать HTML теги.
16 1 Denis Savitskiy
17
h3. Максимальный размер вложения
18
19
Максимально допустимый размер загружаемых файлов (в "киби-байтах":http://ru.wikipedia.org/wiki/Двоичные_приставки). _Стандартный размер: 5120 (5 "меби-байт":http://ru.wikipedia.org/wiki/Двоичные_приставки )_
20
21 5 Ruslan Khasanov
h3. Количество записей на страницу
22 2 Denis Savitskiy
23 1 Denis Savitskiy
Здесь вы можете установить фиксированные значения, которые пользователь может выбрать для отображаемого количества объектов (задач, фиксаций и т.д.) на страницу.
24
25
_Стандартные значения: 25, 50, 100_
26
27 5 Ruslan Khasanov
h3. Количество дней, отображаемых в Действиях
28 2 Denis Savitskiy
29 5 Ruslan Khasanov
Количество дней активности проектов, которые отображаются на вкладке [[RusRedmineProjectActivity|действия]].
30 1 Denis Savitskiy
31 5 Ruslan Khasanov
h3. Имя компьютера
32 1 Denis Savitskiy
33 5 Ruslan Khasanov
Имя хоста и путь к серверу Redmine. Это имя используется для записи URL в письма, отправленные пользователям. Например, имя хоста текущей установки Redmine является redmine.org.
34 1 Denis Savitskiy
35
h3. Протокол
36
37 5 Ruslan Khasanov
Протокол используется для генерации ссылки в уведомлениях по электронной почте. _По умолчанию: http_
38 1 Denis Savitskiy
39 5 Ruslan Khasanov
Ссылки в почтовых отправлениях "динамические", но невозможно определить, что вы используете небезопасный web-сервер (http) или безопасный (https -> http поверх SSL).
40 1 Denis Savitskiy
41
h3. Форматирование текста
42
43 5 Ruslan Khasanov
Метод форматирования, применяемый при заполнении полей "описания" в задачах, новостях, документах...
44 1 Denis Savitskiy
45 5 Ruslan Khasanov
h3. Кешировать форматированный текст
46 1 Denis Savitskiy
47 5 Ruslan Khasanov
Процесс преобразования форматированного исходного текста в HTML происходит каждый раз, когда текст передается в браузер  (например, описание задачи, вики-страницы...). Этот процесс может быть медленным на больших текстах.
48 1 Denis Savitskiy
49 5 Ruslan Khasanov
Данная настройка позволяет включить кэширование преобразованного текста. Кэшированный текст хранится в хранилище кэша, которое может быть определено в настройках @config.action_controller.cache_store@. По умолчанию, хранилище кэша это "MemoryStore":http://api.rubyonrails.org/classes/ActiveSupport/Cache/MemoryStore.html.
50 1 Denis Savitskiy
51 5 Ruslan Khasanov
Если вам необходимо включить кэширование, то настоятельно рекомендуется, чтобы вы использовали другое хранилище кэша, такое как MemCacheStore или FileStore если память ограничена.
52 1 Denis Savitskiy
53 5 Ruslan Khasanov
Вы можете больше узнать о хранилище кэша в руководстве по Rails:
54 1 Denis Savitskiy
http://guides.rubyonrails.org/caching_with_rails.html#cache-stores
55
56
h3. Сжатие истории Wiki
57
58 5 Ruslan Khasanov
Позволяет включить сжатие для хранения истории вики (уменьшает размер базы данных). _По умолчанию: disabled_
59 1 Denis Savitskiy
60 5 Ruslan Khasanov
h3. Ограничение количества заголовков для RSS потока
61 1 Denis Savitskiy
62
Maximum number of records contained in RSS feeds. _Стандартное значение: 15_
63
64 5 Ruslan Khasanov
h3. Максимальный размер текстового файла для отображения
65 1 Denis Savitskiy
66
It provides a way to limit the maximum size of text files which are display inline.
67
68 5 Ruslan Khasanov
h3. Максимальное число строк для diff
69 1 Denis Savitskiy
70
It provides a way to limit the maximum number of diff lines which are displayed by Redmine.
71
72
h2. Display
73
74
h3. Theme
75
76
This option lets you choose a custom theme.
77
Redmine is shipped with two additional themes besides the [[ThemeDefault|default]] theme:
78
* [[ThemeAlternate|alternate]], which mainly provides issue list colorization based on issues priority.
79
* [[ThemeClassic|classic]], which is derived from the Redmine 0.5.1 design and brings a _classic_ look.
80
81
Screenshot of the [[ThemeAlternate|alternate]] theme:
82
83
!alternate_theme.png!
84
85
Themes are located in @public/themes/@. You can read more about [[Themes]].
86
87
h3. Default language
88
89
The default language is selected when the application could not determine the user's browser language. The default language is also used when sending email to multiple users. _Default: English_
90
91
h3. Date format
92
93
Lets you choose how dates are displayed:
94
95
  * *Based on user's language*: dates will be displayed specifically for each user, according to the format defined for its language
96
  * *Other formats*: dates will always be displayed using the specified format
97
98
_Default: Based on user's language_
99
100
h3. Time format
101
102
Lets you choose how times are displayed:
103
104
  * *Based on user's language*: times will be displayed specifically for each user, according to the format defined for its language
105
  * *Other formats*: times will always be displayed using the specified format
106
107
_Default: Based on user's language_
108
109
h3. Users display format
110
111
Lets you choose how usernames are displayed. The following combinations are provided:
112
113
  * _Firstname_
114
  * _Firstname Surname_
115
  * _Surname Firstname_
116
  * _Surname, Firstname_
117
  * _Username_
118
119
h3. Use Gravatar user icons
120
121
If enabled, users "Gravatars":http://en.gravatar.com/ (globally recognized avatar) will be displayed in several places.
122
123
h3. Default Gravatar image
124
125
The image to use for users who don't have a Gravatar.
126
127
h2. Authentication
128
129
h3. Authentication required
130
131
If this option is checked, no page of the application is accessible to anonymous users. Users must sign to access the application. _Default: No_
132
133
h3. Autologin
134
135
This option let users use the auto-login feature. _Default: Disabled_
136
137 3 Ruslan Khasanov
h3. Самостоятельная регистрация
138 1 Denis Savitskiy
139 3 Ruslan Khasanov
Данная настройка позволяет вам включить/отключить самостоятельную регистрацию для новых пользователей:
140 1 Denis Savitskiy
141
* *disabled*: users are not allowed to register
142
* *account activation by email*: new users receive an email containing a link used to activate their accounts (users must provide a valid email address).
143
* *manual account activation* _(default)_: new users' accounts are created but need administrator approval. Administrators receive an email informing them that an account is pending their approval.
144
* *automatic account activation*: new users can log in as soon as they have registered.
145
146
h3. Minimum password length
147
148
Let's the admin decide on the minimum length of the chosen passwords.
149
150
_Default: 4_
151
152
h3. Lost password
153
154
If this option is checked, lost password functionality is available. _Default: Yes_
155
156
h3. Allow OpenID login and registration
157
158
Provides the admin a way to disable OpenID logins and registrations.
159
Note that the setting is immutable as long as the dependency for the feature (an installed copy of the @ruby-openid@ gem) is not met. You can simply install it using @gem install ruby-openid@.
160
161
h2. Projects
162
163
h3. New projects are public by default
164
165
The default state of newly created projects. The project can still be made non-public while creating new project or after the creation of the project.
166
167
h3. Generate sequential project identifiers
168
169
This setting will let Redmine propose sequential project identifiers for you. This can still be manually changed only while creating the project, not afterward.
170
171
h3. Role given to a non-admin user who creates a project
172
173
Defines which role is given by default to a non-admin user who creates a project (this only applies when you have configured Redmine permissions in such a way that non-admin users are actually privileged to create projects).
174
175
h2. Issue tracking
176
177
h3. Allow cross-project issue relations
178
179
If set to true, relations between issues from different projects can be created. _Default: No_
180
181
h3. Display subprojects issues on main projects by default
182
183
If set to true, subprojects issues will be displayed by default on the issue list, calendar and gantt of the main projects (Since r1198). _Default: Yes_
184
185 4 Ruslan Khasanov
h3. Рассчитывать готовность задачи с помощью поля
186 1 Denis Savitskiy
187
Defines how the Issue Done Percentage is set.
188
189
* *Use the issue field* _(default)_: Users can manually set % done.
190
* *Use the issue status*: Each issue status can be assigned a percentage. This enables the [[RedmineIssueTrackingSetup#-Done|"% Done" option for issues]] and the [[RedmineIssueTrackingSetup#Update-issue-done-ratios|"Update issue done ratios" command in the issue statuses overview]].
191
192
h3. Issues export limit
193
194
Maximum number of issues contained in CSV and PDF exports. _Default: 500_
195
196
h3. Default columns displayed on the issue list
197
198
This setting lets you define which columns are displayed on the issue lists by default.
199
Only custom fields that are marked as 'For all projects' can be selected here.
200
201
h2. Email notifications
202
203
h3. Emission mail address
204
205
Email address used in the "From" field of messages sent to users.
206
207
h3. Blind carbon copy recipients (bcc)
208
209
If set to true, email notification will be sent as Blind carbon copy. _Default: Yes_
210
211
h3. Plain text mail
212
213
If set to true, emails are sent in plain text only (no HTML).
214
215
h3. Emails footer
216
217
Here you can enter some text that will be appended to the emails sent by the application.
218
219
h2. Incoming emails
220
221
See for detailed instructions about these settings [[RedmineReceivingEmails]].
222
223
h3. Truncate emails after one of these lines
224
225
These setting can be used to remove signatures from incoming emails.
226
227
h3. Enable WS for incoming emails
228
229
Redmine can be configured to allow issue creation or comments via email. In order to use that feature, you have to enable the API that receives emails. That is where this setting is for. _Default: Off_
230
231
h3. API key
232
233
Within this setting you can enter a secret key used for the issue creation or comments via email feature.
234
235
h2. Repositories
236
237
h3. Autofetch commits
238
239
If this option is activated, the application automatically retrieves the new revisions when a user consults the repository.
240
241
_Default: Yes_
242
243
You can disable this option and automate the call to Repository#fetch_changesets using cron to regularly retrieve the revisions for all of the repositories in the background.
244
Example:
245
<pre>ruby script/runner "Repository.fetch_changesets" -e production</pre>
246
247
You can also call this task from your repository in a post-commit or post-receive hook, so that changesets are fetched after each commit.
248
Here is a tutorial for doing so with git: http://finalcog.com/remine-git-post-receive
249
250
h3. Enable WS for repository management
251
252
This option should be activated only if you installed the script for automatic SVN repository creation. _Default: No_
253
254
h3. Enabled SCM
255
256
Here you can (de)select the SCM-systems Redmine should "provide" to the individual projects. This setting is useful if you only support several SCM-systems (e.g. only Git or only SVN).
257
258
h3. Repositories encodings
259
260
This option lets you specify preferred encodings for repository files (multiple values allowed, comma separated). These encodings are used to convert files content and diff to UTF-8 so that they're properly displayed in the browser.
261
When entering multiple encodings, the first valid encoding regarding the file content is used.
262
263
For French users, this option can be for example set to:
264
265
  UTF-8, ISO 8859-15, CP1252
266
267
For Japanese users:
268
269
  ISO-2022-JP, EUC-JP, UTF-8, SHIF_JIS, WINDOWS-31J
270
271
h3. Maximum number of revisions displayed on file log
272
273
It provides a way to limit the amount of revisions which are retrieved from the SCM for a certain, browsed path.
274
275
h3. Referencing issues in commit messages
276
277
When fetched from the repositories, commit messages are scanned for referenced or fixed issue IDs.
278
These options lets you define keywords that can be used in commit message to reference or fix issues automatically, and the status to apply to fixed issues.
279
280
Default keywords are:
281
282
* for referencing issues: refs, references, IssueID
283
* for fixing issues: fixes, closes
284
285
There's no default status defined for fixed issue. You'll have to specify it if you want to enable auto closure of issues.
286
If you want to reference issues without using keywords, enter a single star: * in the *Referencing keywords* (Administration/Repository) setting. In this case, any issue ID found in the message will be linked to the changeset.
287
288
Example of a working commit message using default keywords:
289
290
  This commit refs #1, #2 and fixes #3
291
292
This message would reference issues 1 and 2 and automatically fix issue 3.
293
After a keyword issue IDs can be separated with a space, a comma or &.