I'm new to Capistrano and I'm struggling to get started. A brief summary of what to do:
-
GIT pull The latest code from our GIT repo, the union builder on the union build server matches the environment of the deployment environment . I want the code to be made here I do not want to make a binary deployment on a Mac laptop, for example
- Compile binary on this machine.
- Deploy it from this machine to all target machines.
- To build the build, we can do all the SSH on a build user build machine.
- The build machine is behind the gateway machine, not directly from the reach.
- It is also a shared user in all deployment target machines and behind the gateway.
- The deployed binary is single executable, and there is an init script on the target machines. After deploying binary and changing the symlink, restart the service through the init script.
- Agent forwarding for all required SSH keys and all necessary functions.
So it seems very simple in principle, but Capisano thinks and is a bit magical, as a result, I am not sure how to accomplish all this. It seems that it wants to check my code and copy it to remote machines, for example without first having to make it
I think I need to ignore the default SmartTrans of Capistranos and just command it on a shell appropriate server in the pseudo code:
-
Gateway Through SSH Buildmachine "CD Repos & amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; amp; "SCP BuildMasin: Repo / Binary." Through SSI TargetM (S); & Lt; MV & amp; Simplic ;; Service Fu Restart "
Is I also the right tool for the job? It seems that there is a lot like a rock climb like a square hole.
Can anyone explain to me what the content of the Captivrano configuration files should be, and the
cap command is run to complete it?
BTW, I have Around -Pass searches and see the questions like and
Old is old, but you do not know when a person needs it ...
First and formost, idea that Capistrano may not be the right tool for the job you want to do this .
He said, it is not impossible to complete what you expect. While large files are deployed and modified in projects (eg CSS / JS Miniature, JS Build etc.) I I want to avoid Receive, in your case, you may want to consider running a "deployment stocks" and configure it as a source Constrino.
- Upload the resulting binary to the deployment repository
- Your operation will look like this:
- Run the local build with whatever device you need
- Upload the resulting binary to the deployment repository
- Castistano will connect to the application server, bring fresh binary from the repository, require any server-side work and symlink to "current"
As a side-effect you can Deployed binary Yes, you are finished with the full history
No comments:
Post a Comment