Project

General

Profile

EsRedmineSettings » History » Version 14

Leonel Iturralde, 2015-04-01 16:28

1 1 Juan Carlos Sabastizagal
h1. Configuración 
2
3
{{>TOC}}
4
5
h2. Configuración General
6
7
h3. Título de la aplicación
8
9 2 Leonel Iturralde
Título que aparece en la cabecera de la aplicación. Este es el enlace justo debajo de la barra de título con « Home/My page/Projects/Help» cuando esta logeado.
10 1 Juan Carlos Sabastizagal
11 3 Leonel Iturralde
h3. Texto de Bienvenida
12 1 Juan Carlos Sabastizagal
13 3 Leonel Iturralde
Texto mostrado en la página principal de Redmine. Este texto puede contener etiquetas HTML.
14 1 Juan Carlos Sabastizagal
15 4 Leonel Iturralde
h3. Tamaño Máximo de Adjunto
16 1 Juan Carlos Sabastizagal
17 6 Leonel Iturralde
Tamaño máximo de archivos subidos (en "kibi-bytes":http://en.wikipedia.org/wiki/Binary_prefix). _Por defecto: 5120 (5 "mebi-bytes":http://en.wikipedia.org/wiki/Binary_prefix )_
18 1 Juan Carlos Sabastizagal
19 5 Leonel Iturralde
h3. Objetos por página
20 1 Juan Carlos Sabastizagal
21 5 Leonel Iturralde
Aquí puedes configurar los valores fijos que los usuarios pueden seleccionar para la cantidad de objectos (peticiones, revisiones, etc.)
22 1 Juan Carlos Sabastizagal
23 5 Leonel Iturralde
_Por Defecto: 25, 50, 100_
24 1 Juan Carlos Sabastizagal
25 7 Leonel Iturralde
h3. Días a mostrar en la actividad de proyecto
26 1 Juan Carlos Sabastizagal
27 7 Leonel Iturralde
El valor inicial (y recurrente mientras navegas) de la cantidad de días que la actividad(es) del proyecto es mostrada en [[EsRedmineProjectActivity|activity]]-tab.
28 1 Juan Carlos Sabastizagal
29 8 Leonel Iturralde
h3. Nombre y Ruta del Servidor
30 1 Juan Carlos Sabastizagal
31 8 Leonel Iturralde
Nombre y Ruta del Servidor de Redmine. Este nombre es utilizado para escribir URL en correo electronicos enviados a usuarios. Ejemplo nombre del servidor de este redmine es redmine.org.
32 1 Juan Carlos Sabastizagal
33 9 Leonel Iturralde
h3. Protocolo
34 1 Juan Carlos Sabastizagal
35 9 Leonel Iturralde
Protocolo usado para generar enlaces en notificaciones de correo electrónicos. _Por Defecto: http_
36 1 Juan Carlos Sabastizagal
37 9 Leonel Iturralde
Enlaces en correo electrónicos son "adivinados", pero no puede determinarse si estás usando un servidor web inseguro (http) or seguro (https -> http sobre SSL).
38 1 Juan Carlos Sabastizagal
39 10 Leonel Iturralde
h3. Formato de Texto
40 1 Juan Carlos Sabastizagal
41 10 Leonel Iturralde
Método de Formateo aplicado a los campos "descripcion" de peticiones, noticias, documentos...
42 1 Juan Carlos Sabastizagal
43 11 Leonel Iturralde
h3. Cachear texto formateado (1.0)
44 1 Juan Carlos Sabastizagal
45 11 Leonel Iturralde
Formateo de Texto transforma texto crudo a HTML y corre cada vez que un texto formateado es enviado al navegador (ejemplo: petición, descripción, página wiki...). Este proceso puede ser lento con textos largos.
46 1 Juan Carlos Sabastizagal
47 11 Leonel Iturralde
Esta configuración te deja almacenar el texto formateado. El texto almacenado es guardado en cache que puede ser configurado con @config.action_controller.cache_store@. Por defecto, este cache es "MemoryStore":http://api.rubyonrails.org/classes/ActiveSupport/Cache/MemoryStore.html.
48 1 Juan Carlos Sabastizagal
49 11 Leonel Iturralde
Si necesitas habilitar el cache, es recomendable que se configure el cache a usar otro cache como MemCacheStore or FileStore si la memoria es un problema.
50 1 Juan Carlos Sabastizagal
51 11 Leonel Iturralde
Puede leer más sobre cache en guías de Rails:
52 1 Juan Carlos Sabastizagal
http://guides.rubyonrails.org/caching_with_rails.html#cache-stores
53
54 12 Leonel Iturralde
h3. Compresión del historial del Wiki
55 1 Juan Carlos Sabastizagal
56 13 Leonel Iturralde
Te deja activar la compresión del historial del wiki (reduce tamaño de base de datos). _Por Defecto: Desabilidato_
57 1 Juan Carlos Sabastizagal
58 14 Leonel Iturralde
h3. Límite de contenido para sindicación
59 1 Juan Carlos Sabastizagal
60 14 Leonel Iturralde
Número Máximo de registros contenidos en canales RSS. _Por Defecto: 15_
61 1 Juan Carlos Sabastizagal
62
h3. Max size of text files displayed inline KB
63
64
It provides a way to limit the maximum size of text files which are display inline.
65
66
h3. Max number of diff lines displayed
67
68
It provides a way to limit the maximum number of diff lines which are displayed by Redmine.
69
70
h2. Display
71
72
h3. Theme
73
74
This option lets you choose a custom theme.
75
Redmine is shipped with two additional themes besides the [[ThemeDefault|default]] theme:
76
* [[ThemeAlternate|alternate]], which mainly provides issue list colorization based on issues priority.
77
* [[ThemeClassic|classic]], which is derived from the Redmine 0.5.1 design and brings a _classic_ look.
78
79
Screenshot of the [[ThemeAlternate|alternate]] theme:
80
81
!alternate_theme.png!
82
83
Themes are located in @public/themes/@. You can read more about [[Themes]].
84
85
h3. Default language
86
87
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_
88
89
h3. Date format
90
91
Lets you choose how dates are displayed:
92
93
  * *Based on user's language*: dates will be displayed specifically for each user, according to the format defined for its language
94
  * *Other formats*: dates will always be displayed using the specified format
95
96
_Default: Based on user's language_
97
98
h3. Time format
99
100
Lets you choose how times are displayed:
101
102
  * *Based on user's language*: times will be displayed specifically for each user, according to the format defined for its language
103
  * *Other formats*: times will always be displayed using the specified format
104
105
_Default: Based on user's language_
106
107
h3. Users display format
108
109
Lets you choose how usernames are displayed. The following combinations are provided:
110
111
  * _Firstname_
112
  * _Firstname Surname_
113
  * _Surname Firstname_
114
  * _Surname, Firstname_
115
  * _Username_
116
117
h3. Use Gravatar user icons
118
119
If enabled, users "Gravatars":http://en.gravatar.com/ (globally recognized avatar) will be displayed in several places.
120
121
h3. Default Gravatar image
122
123
The image to use for users who don't have a Gravatar.
124
125
h2. Authentication
126
127
h3. Authentication required
128
129
If this option is checked, no page of the application is accessible to anonymous users. Users must sign to access the application. _Default: No_
130
131
h3. Autologin
132
133
This option let users use the auto-login feature. _Default: Disabled_
134
135
h3. Self-registration
136
137
This option lets you enable/disable new users self registration:
138
139
* *disabled*: users are not allowed to register
140
* *account activation by email*: new users receive an email containing a link used to activate their accounts (users must provide a valid email address).
141
* *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.
142
* *automatic account activation*: new users can log in as soon as they have registered.
143
144
h3. Minimum password length
145
146
Let's the admin decide on the minimum length of the chosen passwords.
147
148
_Default: 4_
149
150
h3. Lost password
151
152
If this option is checked, lost password functionality is available. _Default: Yes_
153
154
h3. Allow OpenID login and registration
155
156
Provides the admin a way to disable OpenID logins and registrations.
157
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@.
158
159
h2. Projects
160
161
h3. New projects are public by default
162
163
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.
164
165
h3. Generate sequential project identifiers
166
167
This setting will let Redmine propose sequential project identifiers for you. This can still be manually changed only while creating the project, not afterward.
168
169
h3. Role given to a non-admin user who creates a project
170
171
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).
172
173
h2. Issue tracking
174
175
h3. Allow cross-project issue relations
176
177
If set to true, relations between issues from different projects can be created. _Default: No_
178
179
h3. Display subprojects issues on main projects by default
180
181
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_
182
183
h3. Calculate the issue done ratio
184
185
Defines how the Issue Done Percentage is set.
186
187
* *Use the issue field* _(default)_: Users can manually set % done.
188
* *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]].
189
190
h3. Issues export limit
191
192
Maximum number of issues contained in CSV and PDF exports. _Default: 500_
193
194
h3. Default columns displayed on the issue list
195
196
This setting lets you define which columns are displayed on the issue lists by default.
197
Only custom fields that are marked as 'For all projects' can be selected here.
198
199
h2. Email notifications
200
201
h3. Emission mail address
202
203
Email address used in the "From" field of messages sent to users.
204
205
h3. Blind carbon copy recipients (bcc)
206
207
If set to true, email notification will be sent as Blind carbon copy. _Default: Yes_
208
209
h3. Plain text mail
210
211
If set to true, emails are sent in plain text only (no HTML).
212
213
h3. Emails footer
214
215
Here you can enter some text that will be appended to the emails sent by the application.
216
217
h2. Incoming emails
218
219
See for detailed instructions about these settings [[RedmineReceivingEmails]].
220
221
h3. Truncate emails after one of these lines
222
223
These setting can be used to remove signatures from incoming emails.
224
225
h3. Enable WS for incoming emails
226
227
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_
228
229
h3. API key
230
231
Within this setting you can enter a secret key used for the issue creation or comments via email feature.
232
233
h2. Repositories
234
235
h3. Autofetch commits
236
237
If this option is activated, the application automatically retrieves the new revisions when a user consults the repository.
238
239
_Default: Yes_
240
241
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.
242
Example:
243
<pre>ruby script/runner "Repository.fetch_changesets" -e production</pre>
244
245
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.
246
Here is a tutorial for doing so with git: http://finalcog.com/remine-git-post-receive
247
248
h3. Enable WS for repository management
249
250
This option should be activated only if you installed the script for automatic SVN repository creation. _Default: No_
251
252
h3. Enabled SCM
253
254
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).
255
256
h3. Repositories encodings
257
258
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.
259
When entering multiple encodings, the first valid encoding regarding the file content is used.
260
261
For French users, this option can be for example set to:
262
263
  UTF-8, ISO 8859-15, CP1252
264
265
For Japanese users:
266
267
  ISO-2022-JP, EUC-JP, UTF-8, SHIF_JIS, WINDOWS-31J
268
269
h3. Maximum number of revisions displayed on file log
270
271
It provides a way to limit the amount of revisions which are retrieved from the SCM for a certain, browsed path.
272
273
h3. Referencing issues in commit messages
274
275
When fetched from the repositories, commit messages are scanned for referenced or fixed issue IDs.
276
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.
277
278
Default keywords are:
279
280
* for referencing issues: refs, references, IssueID
281
* for fixing issues: fixes, closes
282
283
There's no default status defined for fixed issue. You'll have to specify it if you want to enable auto closure of issues.
284
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.
285
286
Example of a working commit message using default keywords:
287
288
  This commit refs #1, #2 and fixes #3
289
290
This message would reference issues 1 and 2 and automatically fix issue 3.
291
After a keyword issue IDs can be separated with a space, a comma or &.