Best practice for storing configuration strings in separate file

Hi,

I want to share the source code for my Connect IQ App publicly on GitHub.

My App is using a 3rd party service that requires an individual API key for each developer. I do not want to accidentally leak my own API key to the public repo.

Currently my API key is hardcoded in the *.mc code of my main file.

Is there a good way in Monkey C to put things like API keys into a separate file and then include/use it somehow in my other *.mc files when needed?

This way I could add the configuration file to .gitignore to be sure my API key doesn't get accidentally published on the public repository.

Or any other tips for a good way to solve the above problem?

Thanks for your help and suggestions!

Top Replies

All Replies