Commit Graph

8 Commits

Author SHA1 Message Date
52efd4b56b fix dockerfile
Some checks failed
Test / Run unit tests (pull_request) Failing after 2m13s
Test / Run integration tests (pull_request) Failing after 12m19s
2023-07-11 10:31:57 +08:00
a1729e1add Use new CI/CD access token for build. (#5)
Some checks failed
Test / Run unit tests (pull_request) Failing after 49s
Test / Run integration tests (pull_request) Failing after 3m8s
Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com>
Reviewed-on: #5
Co-authored-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
Co-committed-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
2023-07-10 22:40:12 +00:00
0926306330 rename token 2023-07-07 13:09:18 +08:00
2bd312f0d0 49: Use a Personal Access Token to access private modules. (#4)
Some checks failed
Test / Run unit tests (pull_request) Failing after 49s
Test / Run integration tests (pull_request) Failing after 20s
I left it unchanged in the PR, but I would recommend a variable name other than `GITEA_TOKEN`, as I suspect that will be used by Gitea at some future date--like Github use `GITHUB_TOKEN`--and cause confusion since this is not the same token.

Something like `GIT_VDB_TO_TOKEN` might do, since we could follow the `HOST_NAME_TOKEN` pattern for other repos if needed.

Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com>
Reviewed-on: #4
Co-authored-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
Co-committed-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
2023-07-07 04:36:30 +00:00
9b47315024 use access token for gitea 2023-07-07 01:45:43 +08:00
95797252ed dockerfile cleanup 2023-07-03 12:58:41 +08:00
5e8f283897 [dev] docker go build 2023-07-03 12:58:41 +08:00
ccb517bf61 dockerfile, .gitignore 2023-06-23 21:21:14 +08:00