root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

do not use --force command argument for yarn

This commit is contained in:
Mike Greiling 2017-02-16 01:04:08 -06:00
parent eca18c0bd1
commit 2f0d0b510d
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/install/installation.md
View File

@ -468,7 +468,7 @@ Check if GitLab and its environment are configured correctly:
### Compile Assets
sudo -u git -H yarn install --force --pure-lockfile
sudo -u git -H yarn install --production --pure-lockfile
sudo -u git -H bundle exec rake gitlab:assets:compile RAILS_ENV=production NODE_ENV=production
### Start Your GitLab Instance

2
doc/update/8.16-to-8.17.md
View File

@ -118,7 +118,7 @@ sudo -u git -H bundle clean
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Install/update frontend asset dependencies
sudo -u git -H yarn install --force --pure-lockfile
sudo -u git -H yarn install --production --pure-lockfile
# Clean up assets and cache
sudo -u git -H bundle exec rake gitlab:assets:clean gitlab:assets:compile cache:clear RAILS_ENV=production

2
lib/tasks/yarn.rake
View File

@ -24,7 +24,7 @@ namespace :yarn do
desc 'Install Node dependencies with Yarn'
task install: ['yarn:available'] do
unless system('yarn install --force --pure-lockfile --ignore-engines')
unless system('yarn install --pure-lockfile --ignore-engines')
abort 'Error: Unable to install node modules.'.color(:red)
end
end