Multiple deployment environments (production / production / etc) and Facebook applications

Question

I am looking for a “best practice” answer regarding Facebook applications and the middleware / production environment. Instinctively, I provided each environment with my Facebook application, which has its own identifier and secret. It appears ( here , here, and through extensive Google) that it is simply not possible to share the OG configuration through applications, so I copied the application settings in different environments (icon, requested permissions and texts, etc.). It was pain and ugliness, but I lived with it.

Alas, with the introduction of opengraph actions this is no longer funny - much more to copy, and everything must go through the approval process. Is there a better way to do this? The employee suggested that we simply share the same application in all environments, but I’m afraid about this - this means that we will have to share production secrets with the intermediate environment (I’m not even talking about localhost development environments), and that we need to somehow Route Facebook traffic to the correct environment (because one Facebook application means one page URL).

There must be a better way ... no?

Answer 1

Now I see the "Test Apps" function, which seems to match the score: https://developers.facebook.com/docs/apps/test-apps/

Tested applications are similar to regular applications in which they have their own application identifier and independent settings, but they offer several advantages for use during pre-production: ... When creating test applications, settings are copied from your production application, so it’s easy to spin up new ones applications that reflect the settings of your working application

It works for me so far.

Answer 2

I asked almost the same question at the F8 breakthrough session last year. Creating multiple applications is best practice. They know that this is an inconvenience, especially with open objects and graph actions. However, they pointed out the possibility of creating applications in the future through the API, but I'm still waiting for this. Until now, this is a manual process.