woodpecker/cmd/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
..
docs Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
flags.go Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
health.go Fix health check (#2412) 2023-09-09 14:45:24 +02:00
main.go Replace goimports with gci (#3202) 2024-01-14 18:22:06 +01:00
server.go Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
setup.go Use forge from db (#1417) 2024-04-16 08:04:55 +02:00
swagger.go fix and lint swagger file (#3007) 2023-12-24 15:50:01 +01:00
swagger_test.go Add some tests (#3030) 2023-12-27 10:36:49 +01:00
woodpecker_docs_gen.go fix and lint swagger file (#3007) 2023-12-24 15:50:01 +01:00