summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGo MAEDA <maeda@farend.jp>2021-04-03 07:12:43 +0000
committerGo MAEDA <maeda@farend.jp>2021-04-03 07:12:43 +0000
commitb89cb894ebea603b6a10e56d89966a955a64358e (patch)
tree03f5770a41e137c5231c22d5f66ac658e846b64f
parent3b58084ea6fbee3f5d1ee21a1d5dbb7fddd2a268 (diff)
downloadredmine-b89cb894ebea603b6a10e56d89966a955a64358e.tar.gz
redmine-b89cb894ebea603b6a10e56d89966a955a64358e.zip
Remove trailing whitespaces in doc/INSTALL and doc/UPGRADING.
git-svn-id: http://svn.redmine.org/redmine/trunk@20911 e93f8b46-1217-0410-a6f0-8f06a7374b81
-rw-r--r--doc/INSTALL16
-rw-r--r--doc/UPGRADING10
2 files changed, 13 insertions, 13 deletions
diff --git a/doc/INSTALL b/doc/INSTALL
index 48ba41a13..3c2566984 100644
--- a/doc/INSTALL
+++ b/doc/INSTALL
@@ -45,7 +45,7 @@ Optional:
It will be loaded automatically when running `bundle install`.
5. Generate a session store secret
-
+
Redmine stores session data in cookies by default, which requires
a secret to be generated. Under the application main directory run:
bundle exec rake generate_secret_token
@@ -54,33 +54,33 @@ Optional:
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml
6. Create the database structure
-
+
Under the application main directory run:
bundle exec rake db:migrate RAILS_ENV="production"
-
+
It will create all the tables and an administrator account.
7. Setting up permissions (Windows users have to skip this section)
-
+
The user who runs Redmine must have write permission on the following
subdirectories: files, log, tmp & public/plugin_assets.
-
+
Assuming you run Redmine with a user named "redmine":
sudo chown -R redmine:redmine files log tmp public/plugin_assets
sudo chmod -R 755 files log tmp public/plugin_assets
8. Test the installation by running the Puma web server
-
+
Under the main application directory run:
ruby bin/rails server -e production
-
+
Once Puma has started, point your browser to http://localhost:3000/
You should now see the application welcome page.
9. Use the default administrator account to log in:
login: admin
password: admin
-
+
Go to "Administration" to load the default configuration data (roles,
trackers, statuses, workflow) and to adjust the application settings
diff --git a/doc/UPGRADING b/doc/UPGRADING
index a41388136..545aa547e 100644
--- a/doc/UPGRADING
+++ b/doc/UPGRADING
@@ -13,7 +13,7 @@ http://www.redmine.org/
and your configuration file (RAILS_ROOT/config/configuration.yml)
into the new config directory
Note: before Redmine 1.2, SMTP configuration was stored in
- config/email.yml. It should now be stored in config/configuration.yml.
+ config/email.yml. It should now be stored in config/configuration.yml.
3. Copy the RAILS_ROOT/files directory content into your new installation
This directory contains all the attached files.
@@ -43,7 +43,7 @@ http://www.redmine.org/
It will be loaded automatically when running `bundle install`.
6. Generate a session store secret
-
+
If you're upgrading from Redmine 2.x or below, remove the following file
if it exists: config/initializers/secret_token.rb
@@ -62,15 +62,15 @@ http://www.redmine.org/
need to upgrade the plugin migrations before running the plugin migrations
using:
bundle exec rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production"
-
+
Please make a backup before doing this! Under the new application
directory run:
bundle exec rake db:migrate RAILS_ENV="production"
-
+
If you have installed any plugins, you should also run their database
migrations using:
bundle exec rake db:migrate_plugins RAILS_ENV="production"
-
+
8. Clear the cache and the existing sessions by running:
bundle exec rake tmp:cache:clear tmp:sessions:clear