Project

General

Profile

Feature #41754 ยป precompile-assets-instruction.patch

Go MAEDA, 2024-11-14 12:44

View differences:

doc/INSTALL
Alternatively, you can store this secret in config/secrets.yml:
https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml
6. Create the database structure
6. Compile assets
Compile the assets such as stylesheets, javascripts and images. This
generates the files into the public/assets directory for delivery by
the web server.
using:
bundle exec rake assets:precompile RAILS_ENV="production"
If deploying to a sub-uri, set the relative URL root as follows:
bundle exec rake assets:precompile RAILS_ENV="production" RAILS_RELATIVE_URL_ROOT=/sub-uri
If you experience issues with missing assets in the browser, try
removing the public/assets directory before re-running the precompile:
bundle exec rake assets:clobber RAILS_ENV="production"
7. 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)
8. 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/assets.
......
sudo chown -R redmine:redmine files log tmp public/assets
sudo chmod -R 755 files log tmp public/assets
8. Test the installation by running the Puma web server
9. 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:
10. Use the default administrator account to log in:
login: admin
password: admin
doc/UPGRADING
DO NOT REPLACE OR EDIT ANY OTHER FILES.
7. Migrate your database
7. Compile assets
Compile the assets such as stylesheets, javascripts and images. This
generates the files into the public/assets directory for delivery by
the web server.
using:
bundle exec rake assets:precompile RAILS_ENV="production"
If deploying to a sub-uri, set the relative URL root as follows:
bundle exec rake assets:precompile RAILS_ENV="production" RAILS_RELATIVE_URL_ROOT=/sub-uri
If you experience issues with missing assets in the browser, try
removing the public/assets directory before re-running the precompile:
bundle exec rake assets:clobber RAILS_ENV="production"
8. Migrate your database
If you are upgrading to Rails 2.3.14 as part of this migration, you
need to upgrade the plugin migrations before running the plugin migrations
......
migrations using:
bundle exec rake db:migrate_plugins RAILS_ENV="production"
8. Clear the cache and the existing sessions by running:
9. Clear the cache and the existing sessions by running:
bundle exec rake tmp:cache:clear tmp:sessions:clear
9. Restart the application server (e.g. mongrel, thin, passenger)
10. Restart the application server (e.g. mongrel, thin, passenger)
10. Finally go to "Administration -> Roles & permissions" to check/set permissions
11. Finally go to "Administration -> Roles & permissions" to check/set permissions
for new features, if any
== References
    (1-1/1)