woodpecker/server
Anbraten d494b6a959
Use forge from db (#1417)
This is the first step towards support for multiple forges (#138). It
inserts a forge using the currently existing env varaibles into db and
uses this forge from db later on in all places of the code.

closes #621

addresses #138 

# TODO
- [x] add forges table
- [x] add id of forge to repo
- [x] use forge of repo
- [x] add forge from env vars to db if not exists
- [x] migrate repo.ForgeID to the newly generated forge
- [x] support cache with forge from repo
- [x] maybe add forge loading cache? (use LRU cache for forges, I expect
users to have less than 10 forges normally)

---------

Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
2024-04-16 08:04:55 +02:00
..
api Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
badges Replace goimports with gci (#3202) 2024-01-14 18:22:06 +01:00
cache Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
ccmenu Update go module path for major version 2 (#2905) 2023-12-08 08:15:08 +01:00
cron Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
forge Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
grpc Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
logging Fix linter (#3354) 2024-02-08 22:49:07 +01:00
model Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
pipeline Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
pubsub Fix linter (#3354) 2024-02-08 22:49:07 +01:00
queue Enable golangci linter gomnd (#3171) 2024-03-15 18:00:25 +01:00
router Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
services Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
store Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
web Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
config.go Use forge from db (#1417) 2024-04-16 08:04:55 +02:00