zelo72
/
documentation
mirror of https://github.com/mastodon/documentation
1
0
Fork 0
Code Issues 6 Releases Wiki Activity

Add advice on asset compile with limited RAM 

Help users running Mastodon on small VPS environments to compile assets without having to upgrade RAM, making use of the Node “max-old-space-size” flag.
This commit is contained in:
Daniel King 2023-02-11 11:43:22 +00:00 committed by GitHub
parent b458498d25
commit cce405dfb6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/admin/troubleshooting.md
View File

@ -30,3 +30,5 @@ Check that you are specifying the correct environment with `RAILS_ENV=production
## **I encountered a compilation error while executing `RAILS_ENV=production bundle exec rails assets:precompile`, but no more information is given. How to fix it?**
Usually it's because your server ran out of memory while compiling assets. Use a swapfile or increase the swap space to increase the memory capacity. Run `RAILS_ENV=production bundle exec rake tmp:cache:clear` to clear cache, then execute `RAILS_ENV=production bundle exec rails assets:precompile` to compile again. Make sure you clear the cache after a compilation error, or it will show "Everything's OK" but leave the assets unchanged.
Another option for compiling assets in a memory restricted environment would be to limit Node's memory use, for example you can avoid an out of memory exception on a small 2GB VPS by restricting Node to 1.2GB `NODE_OPTIONS="--max-old-space-size=1200" RAILS_ENV=production bundle exec rails assets:precompile`.