Installs apprise and allows config of alerting for successful or failed renewals. Currently only supports renewals, not inital issuing. Not necessarily a problem as I'd hope you'd be watching the logs on first run.
I don't love how I create /config/.renew-list.sh. I should readdress this somehow
@ -4,9 +4,10 @@ Dockerised Certbot that utilises cron to schedule creating and renewing SSL cert
## Tags
I use the [Feature Branch](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow) workflow. The `latest` tag contains all of the latest changes that have been merged from individual feature branches. Feature branches are squashed into `master`.
Pinned releases are created by creating a tag off `master` to capture the repo in a particular state. They are recommended for stability.
|Tag |Description|
|-------|-----------|
|latest |Latest image built from the main branch. Usually coincides with a tagged release.|
|develop|Latest image built from the develop branch. Commits are made to the develop branch before being merged to main. Old versions of `develop` are removed after 14 days.|
echo"Renewal attempt of certificate for ${RENEWAL_DOMAINS} succeeded"
if["${NOTIFY_ON_SUCCESS}"="true"];then
apprise -b "Renewal of certificate for ${RENEWAL_DOMAINS} succeeded"${APPRISE_URL}
fi
else
echo"Renewal attempt of certificate for ${RENEWAL_DOMAINS} failed"
if["${NOTIFY_ON_FAILURE}"="true"];then
apprise -b "Renewal of certificate for ${RENEWAL_DOMAINS} failed"${APPRISE_URL}
fi
fi
}
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.