aboutsummaryrefslogtreecommitdiff
path: root/users/fcuny/notes/Makefile (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-05-11delete MakefileFranck Cuny1-27/+0
This is not needed anymore.
2022-05-11add a script to deploy the siteFranck Cuny1-8/+1
Instead of using the Makefile, move the content to a script. This will be executed by drone later.
2022-03-28convert blog to notesFranck Cuny1-2/+2
Separating the two sites so I can customize them differently.
2021-12-06build: push git branches / tags after deployFranck Cuny1-0/+2
After a successful deploy, push all the branches / tags to origin.
2021-10-21build: be explicit about the image to useFranck Cuny1-1/+1
If we're not explicit, we're trying to run the image tagged `latest', but there's no image with that tag.
2021-09-09build: get the proper version for taggingFranck Cuny1-5/+2
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.
2021-08-24build: sleep before taggingFranck Cuny1-0/+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.
2021-08-15build: tag the repo after a deployFranck Cuny1-2/+7
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`).
2021-08-05build: add a MakefileFranck Cuny1-0/+29
Add a Makefile to take care of most common operations (build, deploy, etc).