kotovalexarian-likes-github/capistrano
1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Code Releases Activity

add page about directory structure on server

Browse source
This commit is contained in:
Thomas Kriechbaumer 2015-01-19 10:42:24 +00:00
parent 2592c12040
commit 533acf9523
2 changed files with 41 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
_includes/navigation.html
View file

@ -11,6 +11,7 @@
<li><a href="/documentation/getting-started/installation/">Installation</a></li>
<li><a href="/documentation/getting-started/configuration/">Configuration</a></li>
<li><a href="/documentation/getting-started/structure/">Structure</a></li>
<li><a href="/documentation/getting-started/preparing-your-application/">Preparing Your Application</a></li>
<li><a href="/documentation/getting-started/flow/">Flow</a></li>
<li><a href="/documentation/getting-started/rollbacks/">Rollbacks</a></li>

40
documentation/getting-started/structure/index.markdown Normal file
View file

@ -0,0 +1,40 @@
---
title: Structure
layout: default
---
Capistrano uses a strictly defined directory hierarchy on each remote server to organise the source code and other deployment-related data. The root path of this structure can be defined with the configuration variable `:deploy_to`.
Assuming your `config/deploy.rb` contains this:
{% highlight ruby %}
set :deploy_to, '/var/www/my_app_name'
{% endhighlight %}
Then inspecting the directories inside `/var/www/my_app_name` looks like this:
{% highlight bash %}
├── current -> /var/www/my_app_name/releases/20150120114500/
├── releases
│   ├── 20150080072500
│   ├── 20150090083000
│   ├── 20150100093500
│   ├── 20150110104000
│   └── 20150120114500
├── repo
│ └── <VCS related data>
├── revisions.log
└── shared
└── <linked_files and linked_dirs>
{% endhighlight %}
* `current` is a symlink pointing to the latest release. This symlink is updated at the end of a successful deployment. If the deployment fails in any step the `current` symlink still points to the old release.
* `releases` holds all deployments in a timestamped folder. These folders are the target of the `current` symlink.
* `repo` holds the version control system configured. In case of a git repository the content will be a raw git repository (e.g. objects, refs, etc.).
* `revisions.log` is used to log every deploy or rollback. Each entry is timestamped and the executing user (username from local machine) is listed. Depending on your VCS data like branchnames or revision numbers are listed as well.
* `shared` contains the `linked_files` and `linked_dirs` which are symlinked into each release. This data persists across deployments and releases. It should be used for things like database configuration files and static and persistent user storage handed over from one release to the next.
The application is completely contained within the path of `:deploy_to`. If you plan on deploying multiple applications to the same server, simply choose a different `:deploy_to` path.