3721c06964
* Add documentation for getting Pusher API keys Some features on dev.to, such as direct messaging, require Pusher to function. This change adds instructions to the docs about how to sign up for a Pusher account and add the API keys for local development. * Add Pusher mention to "Key App tech/services" page in docs
1.7 KiB
1.7 KiB
🔑 Key App tech/services
- We use Puma for the server
- We rely heavily on edge caching with Fastly
- We use Cloudinary for image manipulation/serving
- We use Keen for event storage
- We use Airbrake for error monitoring
- We use Timber for logging
- We use Delayed Job for background workers
- We use Algolia for search
- We use Redcarpet and Rouge for Markdown
- We use Carrierwave/Fog/AWS S3 for image upload/storage
- We use a modified version of InstantClick instead of Turbolinks
- We are hosted on Heroku
- We use Heroku scheduler for scheduled jobs (default)
- We use Sendgrid for API-triggered mailing
- We use Mailchimp for marketing/outreach emails
- We use Figaro for app configuration.
- We use CounterCulture to keep track of association counts (counter caches)
- We use Rolify for role management.
- We use Pundit for authorization.
- We use Service Workers to proxy traffic
- We use Preact for some of the front end. See Frontend for more info
- We use Pusher for realtime communication between the application and users’ browsers.
This list is non-exhaustive. If you see something that belongs here, feel free to add it.