Commit 3de68be6 authored by Craig Norris's avatar Craig Norris

Minor wording updates

Minor updates from recent change to page.
parent dd8eeb87
...@@ -1056,31 +1056,30 @@ sudo yum groupinstall 'Development Tools' ...@@ -1056,31 +1056,30 @@ sudo yum groupinstall 'Development Tools'
### Error compiling GitLab assets ### Error compiling GitLab assets
While compiling assets, you might get the following error: While compiling assets, you may receive the following error message:
```plaintext ```plaintext
Killed Killed
error Command failed with exit code 137. error Command failed with exit code 137.
``` ```
This happens because when a container runs out of memory, YARN automatically kills it. This can occur when Yarn kills a container that runs out of memory. To fix this:
To fix this, first make sure you increase your machine's memory (8GB of memory should be good), 1. Increase your system's memory to at least 8 GB.
and then run the following commands:
1. Clean the assets: 1. Run this command to clean the assets:
```shell ```shell
sudo -u git -H bundle exec rake gitlab:assets:clean RAILS_ENV=production NODE_ENV=production sudo -u git -H bundle exec rake gitlab:assets:clean RAILS_ENV=production NODE_ENV=production
``` ```
1. Run the `yarn` command again to ensure any conflicts are resolved: 1. Run the `yarn` command again to resolve any conflicts:
```shell ```shell
sudo -u git -H yarn install --production --pure-lockfile sudo -u git -H yarn install --production --pure-lockfile
``` ```
1. Recompile assets: 1. Recompile the assets:
```shell ```shell
sudo -u git -H bundle exec rake gitlab:assets:compile RAILS_ENV=production NODE_ENV=production sudo -u git -H bundle exec rake gitlab:assets:compile RAILS_ENV=production NODE_ENV=production
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment