mastodon/Procfile

web: bin/heroku-web
worker: bundle exec sidekiq

# For the streaming API, you need a separate app that shares Postgres and Redis:
#
# heroku create
# heroku buildpacks:add heroku/nodejs
# heroku config:set RUN_STREAMING=true
# heroku addons:attach <main-app>::DATABASE
# heroku addons:attach <main-app>::REDIS
#
# and let the main app use the separate app:
#
# heroku config:set STREAMING_API_BASE_URL=wss://<streaming-app-random>.herokuapp.com -a <main-app>
fix: make Procfile compatible with herokuish (#12685) Co-authored-by: Aurelia <aurelia@serenitylabs.cloud> 2020-08-29 10:00:30 -07:00			`web: bin/heroku-web`
More robust PuSH subscription refreshes (#2799) * Fix #2473 - Use sidekiq scheduler to refresh PuSH subscriptions instead of cron Fix an issue where / in domain would raise exception in TagManager#normalize_domain PuSH subscriptions refresh done in a round-robin way to avoid hammering a single server's hub in sequence. Correct handling of failures/retries through Sidekiq (see also #2613). Optimize Account#with_followers scope. Also, since subscriptions are now delegated to Sidekiq jobs, an uncaught exception will not stop the entire refreshing operation halfway through Fix #2702 - Correct user agent header on outgoing http requests * Add test for SubscribeService * Extract #expiring_accounts into method * Make mastodon:push:refresh no-op * Queues are now defined in sidekiq.yml * Queues are now in sidekiq.yml 2017-05-04 17:23:01 -07:00			`worker: bundle exec sidekiq`
Bind servers to 0.0.0.0 in Procfile (#11378) * Bind to 0.0.0.0 * Make Procfile common to main and streaming apps 2019-07-21 21:16:30 -07:00
			`# For the streaming API, you need a separate app that shares Postgres and Redis:`
			`#`
			`# heroku create`
			`# heroku buildpacks:add heroku/nodejs`
			`# heroku config:set RUN_STREAMING=true`
			`# heroku addons:attach <main-app>::DATABASE`
			`# heroku addons:attach <main-app>::REDIS`
			`#`
			`# and let the main app use the separate app:`
			`#`
Refresh Heroku related thingy for heroku-24 stack This should make it possible to run Puma on Heroku with steps like: ``` $ export HEROKU_APP=<app-name> $ heroku create --addons heroku-postgresql,heroku-redis -s heroku-24 $ heroku buildpacks:add https://github.com/heroku/heroku-buildpack-activestorage-preview $ heroku buildpacks:add https://github.com/heroku/heroku-buildpack-apt $ heroku buildpacks:add heroku/nodejs $ heroku buildpacks:add heroku/ruby $ heroku config:set \ OTP_SECRET=`ruby -r securerandom -e 'puts SecureRandom.hex(64)'` \ RAILS_SERVE_STATIC_FILES=true \ LOCAL_DOMAIN=`heroku domains --json \| jq -r '.[] \| select(.kind=="heroku").hostname'` \ `RAILS_ENV=production bin/rails db:encryption:init \| grep ^ACTIVE_RECORD_ENCRYPTION_` $ git push heroku main $ heroku run rake db:migrate ``` 2024-07-24 18:40:43 -07:00			`# heroku config:set STREAMING_API_BASE_URL=wss://<streaming-app-random>.herokuapp.com -a <main-app>`