Popularity
5.1
Stable
Activity
0.0
Stable
196
4
20
Programming language: Go
License: MIT License
Tags:
Utilities
Latest version: v3.0.2
Death alternatives and similar packages
Based on the "Utilities" category.
Alternatively, view Death alternatives based on common mentions on social networks and blogs.
-
项目文档
🚀Vite+Vue3+Gin拥有AI辅助的基础开发平台,支持TS和JS混用。它集成了JWT鉴权、权限管理、动态路由、显隐可控组件、分页封装、多点登录拦截、资源权限、上传下载、代码生成器、表单生成器和可配置的导入导出等开发必备功能。 -
excelize
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets -
Kopia
Cross-platform backup tool for Windows, macOS & Linux with fast, incremental backups, client-side end-to-end encryption, compression and data deduplication. CLI and GUI included. -
goreporter
A Golang tool that does static analysis, unit testing, code review and generate code quality report. -
create-go-app
✨ A complete and self-contained solution for developers of any qualification to create a production-ready project with backend (Go), frontend (JavaScript, TypeScript) and deploy automation (Ansible, Docker) by running only one CLI command. -
EaseProbe
A simple, standalone, and lightweight tool that can do health/status checking, written in Go. -
filetype
Fast, dependency-free Go package to infer binary file types based on the magic numbers header signature -
boilr
:zap: boilerplate template manager that generates files or directories from template repositories -
beaver
💨 A real time messaging system to build a scalable in-app notifications, multiplayer games, chat apps in web and mobile apps. -
go-underscore
Helpfully Functional Go - A useful collection of Go utilities. Designed for programmer happiness.
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
Promo
coderabbit.ai
Do you think we are missing an alternative of Death or a related project?
Popular Comparisons
README
Death
Simple library to make it easier to manage the death of your application.
Get The Library
Use gopkg.in to import death based on your logger.
Version | Go Get URL | source | doc | Notes |
---|---|---|---|---|
3.x | gopkg.in/vrecan/death.v3 | source | doc | This removes the need for an independent logger. By default death will not log but will return an error if all the closers do not properly close. If you want to provide a logger just satisfy the deathlog.Logger interface. |
2.x | gopkg.in/vrecan/death.v2 | source | doc | This supports loggers who do not return an error from their Error and Warn functions like logrus |
1.x | gopkg.in/vrecan/death.v1 | souce | doc | This supports loggers who do return an error from their Error and Warn functions like seelog |
Example
go get gopkg.in/vrecan/death.v3
Use The Library
package main
import (
DEATH "github.com/vrecan/death"
SYS "syscall"
)
func main() {
death := DEATH.NewDeath(SYS.SIGINT, SYS.SIGTERM) //pass the signals you want to end your application
//when you want to block for shutdown signals
death.WaitForDeath() // this will finish when a signal of your type is sent to your application
}
Close Other Objects On Shutdown
One simple feature of death is that it can also close other objects when shutdown starts
package main
import (
"log"
DEATH "github.com/vrecan/death"
SYS "syscall"
"io"
)
func main() {
death := DEATH.NewDeath(SYS.SIGINT, SYS.SIGTERM) //pass the signals you want to end your application
objects := make([]io.Closer, 0)
objects = append(objects, &NewType{}) // this will work as long as the type implements a Close method
//when you want to block for shutdown signals
err := death.WaitForDeath(objects...) // this will finish when a signal of your type is sent to your application
if err != nil {
log.Println(err)
os.Exit(1)
}
}
type NewType struct {
}
func (c *NewType) Close() error {
return nil
}
Or close using an anonymous function
package main
import (
DEATH "github.com/vrecan/death"
SYS "syscall"
)
func main() {
death := DEATH.NewDeath(SYS.SIGINT, SYS.SIGTERM) //pass the signals you want to end your application
//when you want to block for shutdown signals
death.WaitForDeathWithFunc(func(){
//do whatever you want on death
})
}
Release Process
Rules for release branches:
- If you are releasing a new major version you need to branch off of master into a branch
release-branch.v#
(examplerelease-branch.v2
for a 2.x release) - If you are releasing a minor or patch update to an existing major release make sure to merge master into the release branch
Rules for tagging and publishing the release
When you are ready to publish the release make sure you...
- Merge your changes into the correct release branch.
- Check out the release branch locally (example:
git pull origin release-branch.v3
) - Create a new tag for the specific release version you will publish (example:
git tag v3.0.1
) - Push the tag up to github (example:
git push origin v3.0.1
) - Go to the release tab in github
- Select the target branch as the release branch and type in the tag name (tagname should include
v
so example:v3.0.1
) - Write a title and a well worded description on exactly what is in this change
- Click publish release