Skip to content

Commit 7e34e49

Browse files
author
Andrew Walton
committed
Adding explanation for the .active-revision file created on the remote host
1 parent 52f22f9 commit 7e34e49

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,12 +161,14 @@ $ ls -l <remoteDir>
161161
-rw-rw-r-- 1 ec2-user ec2-user 22616 Dec 1 10:22 index.html:9dd26db
162162
```
163163

164-
Activating a revision would copy the content of the passed revision to `index.html` which would be served up by a web server (such as Nginx) on your remote host. Additionally, it creates
164+
Activating a revision would copy the content of the passed revision to `index.html` which would be served up by a web server (such as Nginx) on your remote host. Activating one of the revisions above would look like this:
165165

166166
```bash
167167
$ ember deploy:activate --revision a644ba4
168168
```
169169

170+
Additionally, activation creates an empty file where the filename is the revision key, with an extension of `.active-revision`. This is what is used to determine the currently active revision on the remote host. On activation, all previous `.active-revision` files are removed and a new one is created, based on the revision being activated.
171+
170172
### When does activation occur?
171173

172174
Activation occurs during the `activate` hook of the pipeline. By default, activation is turned off and must be explicitly enabled by one of the 3 methods above.

0 commit comments

Comments
 (0)