You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, tweets are sent out on successful release from within the controller. There are a few problems with this, though:
The user can get an error on tweet failure, even though upload and release was successful
One might want to send out other notifications on successful upload (e.g., IRC, identi.ca, etc.)
One might want to do other things on successful download, such as execute a command-line utility (e.g, pgxn_api_sync).
So create an interface for adding callbacks on successful release, but where the user doesn't get an error if any callbacks fail. They should be configurable in the configuration file, and easy to implement. Perhaps use Plack middleware as a model.
The text was updated successfully, but these errors were encountered:
I'm working on this now, since I need to rip out the Twitter support anyway. Just adding a trigger to the distributions table that passes the distribution meta JSON as a payload to pg_notify(), and implementing a library to consume various notifications and dispatch to various consumers, including Twitter and Mastodon for now. Will make it pretty straightforward to add new integrations in the future by writing a pretty simple Perl module.
Right now, tweets are sent out on successful release from within the controller. There are a few problems with this, though:
pgxn_api_sync
).So create an interface for adding callbacks on successful release, but where the user doesn't get an error if any callbacks fail. They should be configurable in the configuration file, and easy to implement. Perhaps use Plack middleware as a model.
The text was updated successfully, but these errors were encountered: