| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
This reverts commit 695ceaa28821660e17a1cf819cffebe1b5d8c7ca, reversing
changes made to 5485dbc4db3e141673457475bcda5fc88057739f.
|
| |
|
|
|
| |
This reverts commit b17a839d622bdb36ddbe2e0667559c33e9b7fd8a, reversing
changes made to 695ceaa28821660e17a1cf819cffebe1b5d8c7ca.
|
| | |
|
| |
|
|
|
|
|
|
| |
Updating to latest version of 1.1.1 helps to have a stable `clever
deploy` command.
This commit relies on the output of the command instead of manually
pooling the results with `clever activity` command.
|
| |
|
|
|
|
|
| |
Followup after the fix of #15 it was still missing another case of
"git" usage.
This should be the last fix about this variable 🤞.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Imagine such a usecase:
- project is in `/project`
- executing Ansible in `/ansible` with `clever_app_root: /project`
will fail deploying with the git push with the following error:
```
Not a git repository (or any of the parent directories): .git"
```
This PR fixes this.
|
| |
|
|
|
| |
All variables "namespaced" with the role name is helpful to read
"client" configurations
|
| |
|
|
|
|
|
|
| |
Every other variables are prefixed with `clever_` which makes the
definition of variables clearer from a "app" configuration point of
view.
WDYT?
|
| |
|
|
|
|
|
|
| |
If your build tool only uses a shallow clone of your project, Clever
cloud will fail on first time git push. You need to git push a full
clone of your git repo for the first time deployment to clever.
This PR fixes that.
|
| | |
|
| | |
|
| |
|
