Heroku

  • Every Heroku app runs in at least two environments:

    1. on the Heroku platform (we’ll call that production) and
    2. on your local machine (development).

    En este artículo Managing Multiple Environments for an App se habla de como ahcer mas fácil el proceso de despliegue:

    • The solution is to have a staging environment that is as similar to production as is possible.
    • This can be achieved by creating a second Heroku application that hosts your staging application.
    • With staging, you can check your code in a production-like setting before having it affect your actual users.
    • As you already deploy with git, setting up and managing these multiple remote environments is easy.
  • El artículo Collaborating with Other Developers on Your App explica como poner a los otros miembros del equipo como colaboradores en tu app. Básicamente:

    1. Other developers can be invited to collaborate on your app by their email address:
      $ heroku access:add [email protected]
      Adding [email protected] to myapp collaborators... done
      
    2. Use the heroku access command to see the list of current collaborators:
       $ heroku access
       === theirapp Collaborators
       [email protected] owner
       [email protected]  collaborator
      
    3. You can revoke a collaborator’s access using the heroku access:remove command:
       $ heroku access:remove [email protected]
       Removing [email protected] from theirapp collaborators... done
      
      Como colaborador se debe:
    4. You should clone the app locally. The invitation email includes the name of the app. In this example, the app name is theirapp.
       $ heroku git:clone -a theirapp
      
    5. It’s strongly recommended that you get access to the canonical source code repository for the application (for instance on GitHub) and then use
       $ heroku git:remote
      
      to add a git remote to your checkout

results matching ""

    No results matching ""