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
Since keys are configured per APN::App model, not via configutron, I'm confused by the documentation which has me using configatron.
Do I still need to use configatron to configure the host? Can you please update the front page documentation to clarify, removing any parameters that aren't used.
The text was updated successfully, but these errors were encountered:
You're correct that the configatron certificate parameters are not used any more. However, as per your earlier issue, we're considering an update that defaults to the configatron-based certificates in cases where no APN::App model is associated with a device to which a notification is addressed.
I appreciate all of your feedback as you work with this gem. Although we may not be able to address it all immediately, I do hope to get to it soon.
I'm glad now that I left the configatron stuff in the docs because now in version 0.4.1 it is being used again. There is now a default "app" that is used for devices that are not associated with an APN::App and uses the certs that are stored in config. It is not necessary to put any certs in config as long as you associate each device with an APN::App.
Since keys are configured per APN::App model, not via configutron, I'm confused by the documentation which has me using configatron.
Do I still need to use configatron to configure the host? Can you please update the front page documentation to clarify, removing any parameters that aren't used.
The text was updated successfully, but these errors were encountered: