| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Instead of using the Makefile, move the content to a script. This will
be executed by drone later.
|
| |
|
|
| |
Separating the two sites so I can customize them differently.
|
| |
|
|
| |
After a successful deploy, push all the branches / tags to origin.
|
| |
|
|
|
| |
If we're not explicit, we're trying to run the image tagged `latest',
but there's no image with that tag.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We were evaluating the version of the app when the rule was evaluated,
while we need to get the version after we run `flyctl deploy`.
Since we're tagging a release, let's also annotate the tag.
Remove the `--build-arg` argument to `flyct deploy` since it's being
ignored (same with `docker build`).
Closes #1.
|
| |
|
|
|
|
|
| |
The last deploy was tagged v13, while the version deployed was 14. It's
possible that running `fly info` too quickly after a deploy returns the
incorrect version. Adding a `sleep 5` before running the command for git
tag.
|
| |
|
|
|
|
|
|
| |
If the deployment is successful, tag the repository with the version
being deployed on fly.io.
Don't deploy unless the repository is clean (this is done with the
target `worktree-clean`).
|
|
|
Add a Makefile to take care of most common operations (build, deploy,
etc).
|
