将开放式图形操作,对象和聚合从开发者迁移到生产应用程序 [英] Migrating FB open graph actions, objects and aggregations from dev to production app

查看:113
本文介绍了将开放式图形操作,对象和聚合从开发者迁移到生产应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

黑客Facebook打开图表将项目发布到用户流,目前我已经使用测试应用程序创建了所有的动作/对象/聚合。不过,我希望

Been hacking facebook open graph to publish items to a users stream, currently I have created all of the actions/objects/aggregations using a test app. I will however wish to

a)将其迁移到我们的分段服务器以测试
b)a)完成将其迁移到生产服务器

a) Migrate this to our staging server to test b) Once a) completed migrate this to the production server

由于每个FB应用程序都有自己的域(而且我的登台/ prod有自己的域) - 我有一个应用程序为每个环境。然而,我不希望在应用程序的分段和prod版本上重新创建动作/对象/聚合。有没有人知道实现这一点的方法?

Given each FB app has its own domain (and my staging/prod have their own domains) - I have a app for each environment. I would prefer not however to be re-creating the actions/objects/aggregations on both the staging and prod version of the apps. Does anyone know of a way of achieving this?

推荐答案

你可以创建主域的子域吗?如果是这样,应用可以跨多个子域(这可以在您的开发者设置信息中心中进行设置)。或者,您可以在生产域上执行主要身份验证和权限步骤,然后使用相同的访问令牌重定向到您的登台域(大多数API调用不限于默认应用程序域)。

Can you create subdomains of your main domain? If so, apps will work across multiple subdomains (this can be setup in your Developer Settings Dashboard). Alternatively, you can perform the main authentication and permissions step on your production domain and then redirect to your staging domain, using the same access tokens (most API calls aren't restricted to the app domain by default).

这篇关于将开放式图形操作,对象和聚合从开发者迁移到生产应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆