Feature #41754 ยป precompile-assets-instruction.patch
| doc/INSTALL | ||
|---|---|---|
| 55 | 55 |
Alternatively, you can store this secret in config/secrets.yml: |
| 56 | 56 |
https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml |
| 57 | 57 | |
| 58 |
6. Create the database structure |
|
| 58 |
6. Compile assets |
|
| 59 | ||
| 60 |
Compile the assets such as stylesheets, javascripts and images. This |
|
| 61 |
generates the files into the public/assets directory for delivery by |
|
| 62 |
the web server. |
|
| 63 | ||
| 64 |
using: |
|
| 65 |
bundle exec rake assets:precompile RAILS_ENV="production" |
|
| 66 |
|
|
| 67 |
If deploying to a sub-uri, set the relative URL root as follows: |
|
| 68 |
bundle exec rake assets:precompile RAILS_ENV="production" RAILS_RELATIVE_URL_ROOT=/sub-uri |
|
| 69 |
|
|
| 70 |
If you experience issues with missing assets in the browser, try |
|
| 71 |
removing the public/assets directory before re-running the precompile: |
|
| 72 |
bundle exec rake assets:clobber RAILS_ENV="production" |
|
| 73 | ||
| 74 |
7. Create the database structure |
|
| 59 | 75 | |
| 60 | 76 |
Under the application main directory run: |
| 61 | 77 |
bundle exec rake db:migrate RAILS_ENV="production" |
| 62 | 78 | |
| 63 | 79 |
It will create all the tables and an administrator account. |
| 64 | 80 | |
| 65 |
7. Setting up permissions (Windows users have to skip this section)
|
|
| 81 |
8. Setting up permissions (Windows users have to skip this section)
|
|
| 66 | 82 | |
| 67 | 83 |
The user who runs Redmine must have write permission on the following |
| 68 | 84 |
subdirectories: files, log, tmp & public/assets. |
| ... | ... | |
| 71 | 87 |
sudo chown -R redmine:redmine files log tmp public/assets |
| 72 | 88 |
sudo chmod -R 755 files log tmp public/assets |
| 73 | 89 | |
| 74 |
8. Test the installation by running the Puma web server
|
|
| 90 |
9. Test the installation by running the Puma web server
|
|
| 75 | 91 | |
| 76 | 92 |
Under the main application directory run: |
| 77 | 93 |
ruby bin/rails server -e production |
| ... | ... | |
| 79 | 95 |
Once Puma has started, point your browser to http://localhost:3000/ |
| 80 | 96 |
You should now see the application welcome page. |
| 81 | 97 | |
| 82 |
9. Use the default administrator account to log in:
|
|
| 98 |
10. Use the default administrator account to log in:
|
|
| 83 | 99 |
login: admin |
| 84 | 100 |
password: admin |
| 85 | 101 | |
| doc/UPGRADING | ||
|---|---|---|
| 56 | 56 | |
| 57 | 57 |
DO NOT REPLACE OR EDIT ANY OTHER FILES. |
| 58 | 58 | |
| 59 |
7. Migrate your database |
|
| 59 |
7. Compile assets |
|
| 60 | ||
| 61 |
Compile the assets such as stylesheets, javascripts and images. This |
|
| 62 |
generates the files into the public/assets directory for delivery by |
|
| 63 |
the web server. |
|
| 64 | ||
| 65 |
using: |
|
| 66 |
bundle exec rake assets:precompile RAILS_ENV="production" |
|
| 67 |
|
|
| 68 |
If deploying to a sub-uri, set the relative URL root as follows: |
|
| 69 |
bundle exec rake assets:precompile RAILS_ENV="production" RAILS_RELATIVE_URL_ROOT=/sub-uri |
|
| 70 |
|
|
| 71 |
If you experience issues with missing assets in the browser, try |
|
| 72 |
removing the public/assets directory before re-running the precompile: |
|
| 73 |
bundle exec rake assets:clobber RAILS_ENV="production" |
|
| 74 | ||
| 75 |
8. Migrate your database |
|
| 60 | 76 | |
| 61 | 77 |
If you are upgrading to Rails 2.3.14 as part of this migration, you |
| 62 | 78 |
need to upgrade the plugin migrations before running the plugin migrations |
| ... | ... | |
| 71 | 87 |
migrations using: |
| 72 | 88 |
bundle exec rake db:migrate_plugins RAILS_ENV="production" |
| 73 | 89 | |
| 74 |
8. Clear the cache and the existing sessions by running:
|
|
| 90 |
9. Clear the cache and the existing sessions by running:
|
|
| 75 | 91 |
bundle exec rake tmp:cache:clear tmp:sessions:clear |
| 76 | 92 | |
| 77 |
9. Restart the application server (e.g. mongrel, thin, passenger)
|
|
| 93 |
10. Restart the application server (e.g. mongrel, thin, passenger)
|
|
| 78 | 94 | |
| 79 |
10. Finally go to "Administration -> Roles & permissions" to check/set permissions
|
|
| 95 |
11. Finally go to "Administration -> Roles & permissions" to check/set permissions
|
|
| 80 | 96 |
for new features, if any |
| 81 | 97 | |
| 82 | 98 |
== References |