##// END OF EJS Templates
Merged r11657 from trunk....
Jean-Philippe Lang -
r11428:61a32a50020e
parent child
Show More

The requested changes are too big and content was truncated. Show full diff

1 NO CONTENT: modified file
The requested commit or file is too big and content was truncated. Show full diff
@@ -1,99 +1,99
1 1 == Redmine installation
2 2
3 3 Redmine - project management software
4 4 Copyright (C) 2006-2013 Jean-Philippe Lang
5 5 http://www.redmine.org/
6 6
7 7
8 8 == Requirements
9 9
10 10 * Ruby 1.8.7, 1.9.2 or 1.9.3
11 11 * RubyGems
12 12 * Bundler >= 1.0.21
13 13
14 14 * A database:
15 15 * MySQL (tested with MySQL 5.1)
16 16 * PostgreSQL (tested with PostgreSQL 9.1)
17 * SQLite3 (tested with SQLite 3.6)
17 * SQLite3 (tested with SQLite 3.7)
18 18
19 19 Optional:
20 20 * SCM binaries (e.g. svn, git...), for repository browsing (must be available in PATH)
21 21 * ImageMagick (to enable Gantt export to png images)
22 22
23 23 == Installation
24 24
25 25 1. Uncompress the program archive
26 26
27 27 2. Create an empty utf8 encoded database: "redmine" for example
28 28
29 29 3. Configure the database parameters in config/database.yml
30 30 for the "production" environment (default database is MySQL and ruby1.9)
31 31
32 32 If you're running Redmine with MySQL and ruby1.8, replace the adapter name
33 33 with `mysql`
34 34
35 35 4. Install the required gems by running:
36 36 bundle install --without development test
37 37
38 38 If ImageMagick is not installed on your system, you should skip the installation
39 39 of the rmagick gem using:
40 40 bundle install --without development test rmagick
41 41
42 42 If you need to load some gems that are not required by Redmine core (eg. fcgi),
43 43 you can create a file named Gemfile.local at the root of your redmine directory.
44 44 It will be loaded automatically when running `bundle install`.
45 45
46 46 5. Generate a session store secret
47 47
48 48 Redmine stores session data in cookies by default, which requires
49 49 a secret to be generated. Under the application main directory run:
50 50 rake generate_secret_token
51 51
52 52 6. Create the database structure
53 53
54 54 Under the application main directory run:
55 55 rake db:migrate RAILS_ENV="production"
56 56
57 57 It will create all the tables and an administrator account.
58 58
59 59 7. Setting up permissions (Windows users have to skip this section)
60 60
61 61 The user who runs Redmine must have write permission on the following
62 62 subdirectories: files, log, tmp & public/plugin_assets.
63 63
64 64 Assuming you run Redmine with a user named "redmine":
65 65 sudo chown -R redmine:redmine files log tmp public/plugin_assets
66 66 sudo chmod -R 755 files log tmp public/plugin_assets
67 67
68 68 8. Test the installation by running the WEBrick web server
69 69
70 70 Under the main application directory run:
71 71 ruby script/rails server -e production
72 72
73 73 Once WEBrick has started, point your browser to http://localhost:3000/
74 74 You should now see the application welcome page.
75 75
76 76 9. Use the default administrator account to log in:
77 77 login: admin
78 78 password: admin
79 79
80 80 Go to "Administration" to load the default configuration data (roles,
81 81 trackers, statuses, workflow) and to adjust the application settings
82 82
83 83 == SMTP server Configuration
84 84
85 85 Copy config/configuration.yml.example to config/configuration.yml and
86 86 edit this file to adjust your SMTP settings.
87 87 Do not forget to restart the application after any change to this file.
88 88
89 89 Please do not enter your SMTP settings in environment.rb.
90 90
91 91 == References
92 92
93 93 * http://www.redmine.org/wiki/redmine/RedmineInstall
94 94 * http://www.redmine.org/wiki/redmine/EmailConfiguration
95 95 * http://www.redmine.org/wiki/redmine/RedmineSettings
96 96 * http://www.redmine.org/wiki/redmine/RedmineRepositories
97 97 * http://www.redmine.org/wiki/redmine/RedmineReceivingEmails
98 98 * http://www.redmine.org/wiki/redmine/RedmineReminderEmails
99 99 * http://www.redmine.org/wiki/redmine/RedmineLDAP
@@ -1,69 +1,79
1 1 == Redmine upgrade
2 2
3 3 Redmine - project management software
4 4 Copyright (C) 2006-2013 Jean-Philippe Lang
5 5 http://www.redmine.org/
6 6
7 7
8 8 == Upgrading
9 9
10 10 1. Uncompress the program archive in a new directory
11 11
12 12 2. Copy your database settings (RAILS_ROOT/config/database.yml)
13 13 and your configuration file (RAILS_ROOT/config/configuration.yml)
14 14 into the new config directory
15 15 Note: before Redmine 1.2, SMTP configuration was stored in
16 16 config/email.yml. It should now be stored in config/configuration.yml.
17 17
18 18 3. Copy the RAILS_ROOT/files directory content into your new installation
19 19 This directory contains all the attached files.
20 20
21 21 4. Copy the folders of the installed plugins and themes into new installation
22 22 Plugins must be stored in the [redmine_root]/plugins directory
23 23 Themes must be stored in the [redmine_root]/public/themes directory
24 24
25 25 WARNING: plugins from your previous Redmine version may not be compatible
26 26 with the Redmine version you're upgrading to.
27 27
28 28 5. Install the required gems by running:
29 29 bundle install --without development test
30 30
31 31 If ImageMagick is not installed on your system, you should skip the installation
32 32 of the rmagick gem using:
33 33 bundle install --without development test rmagick
34 34
35 Only the gems that are needed by the adapters you've specified in your database
36 configuration file are actually installed (eg. if your config/database.yml
37 uses the 'mysql2' adapter, then only the mysql2 gem will be installed). Don't
38 forget to re-run `bundle install` when you change config/database.yml for using
39 other database adapters.
40
41 If you need to load some gems that are not required by Redmine core (eg. fcgi),
42 you can create a file named Gemfile.local at the root of your redmine directory.
43 It will be loaded automatically when running `bundle install`.
44
35 45 6. Generate a session store secret
36 46
37 47 Redmine stores session data in cookies by default, which requires
38 48 a secret to be generated. Under the new application directory run:
39 49 rake generate_secret_token
40 50
41 51 DO NOT REPLACE OR EDIT ANY OTHER FILES.
42 52
43 53 7. Migrate your database
44 54
45 55 If you are upgrading to Rails 2.3.14 as part of this migration, you
46 56 need to upgrade the plugin migrations before running the plugin migrations
47 57 using:
48 58 rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production"
49 59
50 60 Please make a backup before doing this! Under the new application
51 61 directory run:
52 62 rake db:migrate RAILS_ENV="production"
53 63
54 64 If you have installed any plugins, you should also run their database
55 65 migrations using:
56 66 rake db:migrate_plugins RAILS_ENV="production"
57 67
58 68 8. Clear the cache and the existing sessions by running:
59 69 rake tmp:cache:clear
60 70 rake tmp:sessions:clear
61 71
62 72 9. Restart the application server (e.g. mongrel, thin, passenger)
63 73
64 74 10. Finally go to "Administration -> Roles & permissions" to check/set permissions
65 75 for new features, if any
66 76
67 77 == References
68 78
69 79 * http://www.redmine.org/wiki/redmine/RedmineUpgrade
General Comments 0
You need to be logged in to leave comments. Login now