config.php 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  1. <?php
  2. use Rocketeer\Services\Connections\ConnectionsHandler;
  3. return [
  4. // The name of the application to deploy
  5. // This will create a folder of the same name in the root directory
  6. // configured above, so be careful about the characters used
  7. 'application_name' => 'platform-trace',
  8. // Plugins
  9. ////////////////////////////////////////////////////////////////////
  10. // The plugins to load
  11. 'plugins' => [// 'Rocketeer\Plugins\Slack\RocketeerSlack',
  12. ],
  13. // Logging
  14. ////////////////////////////////////////////////////////////////////
  15. // The schema to use to name log files
  16. 'logs' => function (ConnectionsHandler $connections) {
  17. return sprintf('%s-%s-%s.log', $connections->getConnection(), $connections->getStage(), date('Ymd'));
  18. },
  19. // Remote access
  20. //
  21. // You can either use a single connection or an array of connections
  22. ////////////////////////////////////////////////////////////////////
  23. // The default remote connection(s) to execute tasks on
  24. 'default' => ['beta'],
  25. // The various connections you defined
  26. // You can leave all of this empty or remove it entirely if you don't want
  27. // to track files with credentials : Rocketeer will prompt you for your credentials
  28. // and store them locally
  29. 'connections' => [
  30. 'production' => [
  31. 'host' => '47.92.131.85:2345',
  32. 'username' => 'root',
  33. 'password' => '',
  34. 'key' => '/root/.ssh/id_rsa',
  35. 'keyphrase' => '',
  36. 'agent' => '',
  37. ],
  38. ],
  39. /*
  40. * In most multiserver scenarios, migrations must be run in an exclusive server.
  41. * In the event of not having a separate database server (in which case it can
  42. * be handled through connections), you can assign a 'db_role' => true to the
  43. * server's configuration and it will only run the migrations in that specific
  44. * server at the time of deployment.
  45. */
  46. 'use_roles' => false,
  47. // Contextual options
  48. //
  49. // In this section you can fine-tune the above configuration according
  50. // to the stage or connection currently in use.
  51. // Per example :
  52. // 'stages' => array(
  53. // 'staging' => array(
  54. // 'scm' => array('branch' => 'staging'),
  55. // ),
  56. // 'production' => array(
  57. // 'scm' => array('branch' => 'master'),
  58. // ),
  59. // ),
  60. ////////////////////////////////////////////////////////////////////
  61. 'on' => [
  62. // Stages configurations
  63. 'stages' => [],
  64. // Connections configuration
  65. 'connections' => [
  66. 'production' => [
  67. 'remote' => [
  68. 'root_directory' => '/data/wwwroot/uptoyo/api'
  69. ],
  70. 'scm' => [
  71. 'branch' => 'release'
  72. ]
  73. ]
  74. ],
  75. ],
  76. ];