955bdcb2bc
* Rename all GitHub links from thepracticaldev/dev.to to forem/forem * Use new site name * Rename to Forem * Rename more dev.to to forem * Remove unnecessary redirects * Rename DEV to Forem * Use Forem instead of DEV for branding * Use Forem instead of DEV for licensing * Use seedling instead of DEV logo
2.6 KiB
2.6 KiB
| title |
|---|
| Stack |
🔑 Key App tech/services
For the Forem tech stack we use:
- Puma as the web server
- PostgreSQL as the primary database
- Redis to store cached data
- Fastly for edge caching
- Cloudinary for image manipulation/serving
- Honeybadger for error monitoring
- Timber for logging
- Sidekiq and Active Job for background workers
- Elasticsearch for in app searching
- Ransack for internal search
- Redcarpet and Rouge to parse Markdown
- Carrierwave, Fog and AWS S3 for image upload/storage
- InstantClick (a modified version) instead of Turbolinks to accelerate navigation
- ImageMagick to manipulate images on upload
- Heroku for hosting
- Heroku scheduler for scheduled jobs
- Sendgrid for transactional mailing
- Mailchimp for marketing/outreach emails
- Figaro for app configuration
- CounterCulture to keep track of association counts (counter caches)
- Rolify for role management
- Pundit for authorization
- Service Workers to proxy traffic
- Preact for some of the frontend. See the Frontend Guide for more info
- Pusher for realtime communication between the application and users' browsers
- GitDocs for beautiful and SEO-friendly documentation
- Git for version control
- GitHub for hosting the source code and issue tracking
This list is non-exhaustive. If you see something that belongs here, feel free to add it.