dockerfile alpine linux imagemagick rails

backup: Regularly backups the database as a dump via CRON to an Amazon S3 bucket.redis: In-memory key/value store (used by Sidekiq, ActionCable and for caching).It contains the same Rails code, but only runs Sidekiq The image is based on the Alpine variant of the official Ruby image and uses multi-stage building. It contains the Rails code to handle web requests (by using the Puma gem). The whole stack is divided into multiple different containers: The techniques used to build the app should not be considered as 'best practice', maybe there are better ways to build. This project demonstrates my way of building Rails applications. Sending HTML e-mails with Premailer and the Really Simple Responsive HTML Email Template.User authentication with the Clearance gem.Infinitive scrolling (using the Kaminari gem and some JavaScript).Cron scheduling with Sidekiq-Cron to handle daily data updates from Wikipedia.Background jobs with ActiveJob and the Sidekiq gem (to handle full text indexing, image processing and ActionCable broadcasting).Uploading images directly to S3 with the Shrine gem and jQuery-File-Upload.Editing HTML content with the WYSIWYG JavaScript editor Trix.Full text search via OpenSearch and the Searchkick gem to find post content (with suggestions).

Auto refresh via ActionCable: If a displayed post gets changed by another user/instance, it refreshes automatically using the publish/subscribe pattern.Therefore it's based on the official Alpine Ruby image, uses multi-stage building and some optimizations that I described in my blog. This project aims to build a lean Docker image for use in production. Beside the boring CRUD functionality it has some non-default features. The application is a very simple kind of CMS (content management system) allowing to manage posts. Simple Rails 7.0 application to demonstrate using Docker for production deployment.

Dockerfile alpine linux imagemagick rails