Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarification in configuration documentation #4

Closed
michaelkirk opened this issue Oct 27, 2010 · 2 comments
Closed

clarification in configuration documentation #4

michaelkirk opened this issue Oct 27, 2010 · 2 comments

Comments

@michaelkirk
Copy link

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.

@rebeccanesson
Copy link

Hi Michael,

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.

Best,
Rebecca

@rebeccanesson
Copy link

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.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants