Correct. We removed it in favor of using Postgres full-text search because a JVM running Elasticsearch consumed more memory than the entire rest of the stack combined on a self-host instance.
I am using some other operator to manage each component separately.
Nice. That looks very much like where I landed, too. I don't have imgproxy running, but I should. Serving raw images can give away sensitive personal information (name and time/location the photo was taken) when they're uploaded to the Forem instance from a phone and imgproxy strips that out.
Running into couple of issue with my deployment, exactly not sure what is causing it, I wonder if you are seeing something similar with your deployment, when you have time possible to go through this issues.
Correct. We removed it in favor of using Postgres full-text search because a JVM running Elasticsearch consumed more memory than the entire rest of the stack combined on a self-host instance.
Nice. That looks very much like where I landed, too. I don't have imgproxy running, but I should. Serving raw images can give away sensitive personal information (name and time/location the photo was taken) when they're uploaded to the Forem instance from a phone and imgproxy strips that out.
Running into couple of issue with my deployment, exactly not sure what is causing it, I wonder if you are seeing something similar with your deployment, when you have time possible to go through this issues.
issue fixed forget to tun
bundle exec sidekiq -c 2