Advertisement
Guest User

Untitled

a guest
Aug 24th, 2018
330
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.55 KB | None | 0 0
  1.  
  2. {
  3. // This is the default environment. To change your app to use
  4. // a different env, set NODE_ENV (http://expressjs.com/api.html#app.configure)
  5. "development": {
  6. // This is the port your Express server will listen on
  7. "port": 3000,
  8. //Use 'unauthorized.hbs' template for displaying an error page
  9. "errorTemplate": true
  10.  
  11. // alassian-connect-express currently integrates with JugglingDB for persistence
  12. // to store the host client information (i.e., client key, host public
  13. // key, etc). When no adapter is specified, it defaults to JugglingDB's
  14. // fallback memory storage.
  15. //
  16. // To specify a backend for JugglingDB other than "memory", set the
  17. // "type" value to one of Juggling's other supported types. See
  18. // https://github.com/1602/jugglingdb for more information.
  19. //
  20. // To use your own storage adapter, add the key
  21. // "adapter" to the following configuration, and replace "type" and
  22. // "connection" with any values your adapter expects. Then make sure
  23. // that you register your adapter factory with the following code in
  24. // app.js:
  25. //
  26. // ac.store.register(adapterName, factoryFn)
  27. //
  28. // See atlassian-connect-express/lib/store/index.js and the default jugglingdb.js
  29. // files for code demonstrating how to write a conformant adapter. The
  30. // default values are as follows:
  31. //
  32. // "store": {
  33. // "adapter": "jugglingdb",
  34. // "type": "memory"
  35. // },
  36. //
  37. // To instead configure, say, a PostgreSQL store, the following could be
  38. // used:
  39. //
  40. // "store": {
  41. // "adapter": "jugglingdb",
  42. // "type": "postgres",
  43. // "url": "postgres://localhost/my_addon_database"
  44. // },
  45. //
  46. // "store": {
  47. // "adapter": "jugglingdb",
  48. // "type": "sqlite3",
  49. // "database": "store.db"
  50. // }
  51. },
  52. // This is the production add-on configuration, which is enabled by setting
  53. // the NODE_ENV=production environment variable.
  54. "production": {
  55. // On a PaaS host like Heroku, the runtime environment will provide the
  56. // HTTP port to you via the PORT environement variable, so we configure
  57. // that to be honored here.
  58. "port": "$PORT",
  59. //Use 'unauthorized.hbs' template for displaying an error page
  60. "errorTemplate": true,
  61. // This is the public URL to your production add-on.
  62. "localBaseUrl": "http://xxxxxxxxxx.us-west-2.elb.amazonaws.com",
  63. "store": {
  64. // You won't want to use the memory store in production, or your install
  65. // registrations will be forgotten any time your app restarts. Here
  66. // we tell atlassian-connect-express to use the PostgreSQL backend for the default
  67. // JugglingDB adapter.
  68. "type": "postgres",
  69. // Again, a PaaS host like Heroku will probably provide the db connection
  70. // URL to you through the environment, so we tell atlassian-connect-express to use that value.
  71. "url": "$DATABASE_URL"
  72. },
  73. // Make sure that your add-on can only be registered by the hosts on
  74. // these domains.
  75. "whitelist": [
  76. "*.jira-dev.com",
  77. "*.atlassian.net",
  78. "*.atlassian.com",
  79. "*.jira.com"
  80. ]
  81. },
  82. "product": "confluence"
  83. }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement