No description
Find a file
release-bot fca1fe2b7b
All checks were successful
ci/woodpecker/push/99-release-bot Pipeline was successful
ci/woodpecker/push/0-pre Pipeline was successful
ci/woodpecker/tag/0-pre Pipeline was successful
ci/woodpecker/push/1-build-check Pipeline was successful
ci/woodpecker/push/10-build-dev Pipeline was successful
ci/woodpecker/tag/20-build-tag Pipeline was successful
🎉 Release 1.0.0 (#9)
This PR was opened by the [ready-release-go](https://github.com/woodpecker-ci/plugin-ready-release-go) plugin. When you're ready to do a release, you can merge this pull-request and a new release with version `1.0.0` will be created automatically. If you're not ready to do a release yet, that's fine, whenever you add more changes to `main` this pull-request will be updated.

## Options

- [ ] Mark this version as a release candidate

## [1.0.0](https://git.hackmi.ch/Phil/goshorly/releases/tag/v1.0.0) - 2025-04-07

### 💥 Breaking changes

- [CI Workflow] Improvments for next releses and logic [[#11](#11)]

### 🔒 Security

- [CI-Build] Changed DIND to DIND rootless [[#10](#10)]
- Update docker Docker tag to v28 [[#5](#5)]

###  Features

- Configure Renovate [[#1](#1)]

### 📚 Documentation

- Cleaned README and refresh information [[#12](#12)]

### 📦️ Dependency

- Update dependency go to v1.24.2 [[#8](#8)]
- Update module github.com/gofiber/template/html/v2 to v2.1.3 [[#3](#3)]
- Update dependency font-awesome to v6.7.2 [[#4](#4)]
- Update woodpeckerci/plugin-docker-buildx Docker tag to v5 [[#7](#7)]
- Update module github.com/gofiber/fiber/v2 to v2.52.6 [[#2](#2)]

Co-authored-by: oauth <release_mail>
Reviewed-on: #9
Co-authored-by: release-bot <release-bot@noreply.email>
Co-committed-by: release-bot <release-bot@noreply.email>
2025-04-07 17:44:01 +00:00
.woodpecker [CI Workflow] Improvments for next releses and logic (#11) 2025-04-07 17:41:41 +00:00
db Changed nemspace to correct gitserver 2023-09-04 20:59:51 +02:00
routes [CI Workflow] Improvments for next releses and logic (#11) 2025-04-07 17:41:41 +00:00
utils [CI Workflow] Improvments for next releses and logic (#11) 2025-04-07 17:41:41 +00:00
views [CI Workflow] Improvments for next releses and logic (#11) 2025-04-07 17:41:41 +00:00
.gitignore Update .gitignore 2021-12-08 11:38:57 +01:00
CHANGELOG.md 🎉 Release 1.0.0 (#9) 2025-04-07 17:44:01 +00:00
docker-compose-proxy.yml Changed nemspace to correct gitserver 2023-09-04 20:59:51 +02:00
docker-compose.yml Changed nemspace to correct gitserver 2023-09-04 20:59:51 +02:00
Dockerfile [CI Workflow] Improvments for next releses and logic (#11) 2025-04-07 17:41:41 +00:00
go.mod Update dependency go to v1.24.2 2025-04-05 18:30:54 +00:00
go.sum [deps] updated / [CI] Workflow updated 2025-04-05 20:08:40 +02:00
LICENSE Add LICENSE 2021-12-07 21:30:15 +01:00
main.go Update Fiber and packages 2024-04-19 16:54:09 +02:00
README.md Cleaned README and refresh information (#12) 2025-04-07 17:42:17 +00:00
renovate.json Add renovate.json 2025-04-04 14:34:55 +00:00

status-badge

Goshorly

Easy-to-use, self-hosted link shortener built with Golang and Redis.

Lightweight, fast, and Docker-compatible for seamless deployment. ❤️


Features

  • Self-hosted: Take control of your link shortening service.
  • Built with Golang: High performance and reliability.
  • Redis Integration: Efficient data storage.
  • Easy Deployment: Docker, Binary, Build it yourself
  • Docker Support: ( linux/amd64, linux/arm64 )

Installation

Using Docker

(please refer to the example files!)

git clone https://github.com/yourusername/goshorly.git
cd goshorly
docker-compose up -d

To simplify your deployment, we offer the following Docker tags:

  • dev: Latest code from the main branch (experimental).
  • latest: Latest stable release (may include breaking changes).
  • Versioned Tags (vX, vX.X, vX.X.X): Specific release versions.

Using Binary

  1. Download the latest binary from the releases.
  2. Create an .env file (or use the .env.example) and change the values for your environment.
  3. Run the binary the terminal.

Contributing

We welcome contributions! If you have feature requests, bug reports, or improvements, feel free to:

  • Open an issue.
  • Fork the repository.
  • Create a new branch (feature/awesome-feature).
  • Submit a pull request with detailed explanations.
  • Submit a review.