config.php 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  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' => 'order-manage',
  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' => ['production'],
  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.174.125:2345',
  32. 'username' => 'root',
  33. 'password' => '',
  34. 'key' => '/root/.ssh/id_rsa',
  35. 'keyphrase' => '',
  36. 'agent' => '',
  37. 'db_role' => true,
  38. ],
  39. ],
  40. /*
  41. * In most multiserver scenarios, migrations must be run in an exclusive server.
  42. * In the event of not having a separate database server (in which case it can
  43. * be handled through connections), you can assign a 'db_role' => true to the
  44. * server's configuration and it will only run the migrations in that specific
  45. * server at the time of deployment.
  46. */
  47. 'use_roles' => false,
  48. // Contextual options
  49. //
  50. // In this section you can fine-tune the above configuration according
  51. // to the stage or connection currently in use.
  52. // Per example :
  53. // 'stages' => array(
  54. // 'staging' => array(
  55. // 'scm' => array('branch' => 'staging'),
  56. // ),
  57. // 'production' => array(
  58. // 'scm' => array('branch' => 'master'),
  59. // ),
  60. // ),
  61. ////////////////////////////////////////////////////////////////////
  62. 'on' => [
  63. // Stages configurations
  64. 'stages' => [],
  65. // Connections configuration
  66. 'connections' => [],
  67. ],
  68. ];