From 5680e449831cf45e82b29e394ad2083f1bb9c288 Mon Sep 17 00:00:00 2001
From: umonaca <53662960+umonaca@users.noreply.github.com>
Date: Tue, 30 Jun 2020 07:17:04 -0400
Subject: [PATCH] Add troubleshooting for compilation error (#782)

* Add troubleshooting item

* Minor changes
---
 content/en/admin/troubleshooting.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/en/admin/troubleshooting.md b/content/en/admin/troubleshooting.md
index fafd7e57..07d91e1e 100644
--- a/content/en/admin/troubleshooting.md
+++ b/content/en/admin/troubleshooting.md
@@ -26,3 +26,6 @@ Check that you have run `RAILS_ENV=production bin/rails db:migrate` after the up
 
 Check that you are specifying the correct environment with `RAILS_ENV=production` before the command. By default, the environment is assumed to be development, so the code tries to load development-related gems. However, in production environments, we avoid installing those gems, and that’s where the error comes from.
 
+## **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.