This website works better with JavaScript.
Home
Explore
Help
Sign In
closed-social
/
mastodon
Watch
3
Star
0
Fork
2
Code
Issues
5
Pull Requests
0
Projects
0
Releases
3
Wiki
Activity
闭社主体
https://thu.closed.social
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7025
Commits
4
Branches
567 MiB
Tree:
67b3b62b98
closed-social-glitch-2
closed-social-v3
cs+3.4.6
master
v0.1.2
v0.1.1
v0.1.0
Branches
Tags
${ item.name }
Create branch
${ searchTerm }
from '67b3b62b98'
${ noResults }
mastodon
/
Procfile
2 lines
68 B
Raw
Normal View
History
Add Heroku deployment support
7 years ago
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
7 years ago
web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq