|
|
|
|
|
|
|
|
It will be loaded automatically when running `bundle install`. |
|
|
It will be loaded automatically when running `bundle install`. |
|
|
|
|
|
|
|
|
5. Generate a session store secret |
|
|
5. Generate a session store secret |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Redmine stores session data in cookies by default, which requires |
|
|
Redmine stores session data in cookies by default, which requires |
|
|
a secret to be generated. Under the application main directory run: |
|
|
a secret to be generated. Under the application main directory run: |
|
|
bundle exec rake generate_secret_token |
|
|
bundle exec rake generate_secret_token |
|
|
|
|
|
|
|
|
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml |
|
|
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml |
|
|
|
|
|
|
|
|
6. Create the database structure |
|
|
6. Create the database structure |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Under the application main directory run: |
|
|
Under the application main directory run: |
|
|
bundle exec rake db:migrate RAILS_ENV="production" |
|
|
bundle exec rake db:migrate RAILS_ENV="production" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It will create all the tables and an administrator account. |
|
|
It will create all the tables and an administrator account. |
|
|
|
|
|
|
|
|
7. Setting up permissions (Windows users have to skip this section) |
|
|
7. Setting up permissions (Windows users have to skip this section) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The user who runs Redmine must have write permission on the following |
|
|
The user who runs Redmine must have write permission on the following |
|
|
subdirectories: files, log, tmp & public/plugin_assets. |
|
|
subdirectories: files, log, tmp & public/plugin_assets. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Assuming you run Redmine with a user named "redmine": |
|
|
Assuming you run Redmine with a user named "redmine": |
|
|
sudo chown -R redmine:redmine files log tmp public/plugin_assets |
|
|
sudo chown -R redmine:redmine files log tmp public/plugin_assets |
|
|
sudo chmod -R 755 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 |
|
|
8. Test the installation by running the Puma web server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Under the main application directory run: |
|
|
Under the main application directory run: |
|
|
ruby bin/rails server -e production |
|
|
ruby bin/rails server -e production |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Once Puma has started, point your browser to http://localhost:3000/ |
|
|
Once Puma has started, point your browser to http://localhost:3000/ |
|
|
You should now see the application welcome page. |
|
|
You should now see the application welcome page. |
|
|
|
|
|
|
|
|
9. Use the default administrator account to log in: |
|
|
9. Use the default administrator account to log in: |
|
|
login: admin |
|
|
login: admin |
|
|
password: admin |
|
|
password: admin |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Go to "Administration" to load the default configuration data (roles, |
|
|
Go to "Administration" to load the default configuration data (roles, |
|
|
trackers, statuses, workflow) and to adjust the application settings |
|
|
trackers, statuses, workflow) and to adjust the application settings |
|
|
|
|
|
|