Move Gitea and Drone CI to new VMs #396
No reviewers
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#396
Loading…
Reference in New Issue
No description provided.
Delete Branch "chore/move_gitea_and_drone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #300, #302, #355, #388
(Paired with @greg on everything.)
Move Gitea and Drone CI to new VMsto WIP: Move Gitea and Drone CI to new VMsTurned out afterwards that the containers being created to execute the actual builds are unable to connect to
gitea.kosmos.org
via HTTP (i.e. unable to git-clone the repos). I looked at it for quite some time, but we have yet to find a solution.b98a09e941
to0a953070fe
WIP: Move Gitea and Drone CI to new VMsto Move Gitea and Drone CI to new VMsFixed the connection issues by using the new subdomain
lb.kosmos.org
with A records (just one at the moment, but we can then add more when all the hosts run the same proxy config), and changing the CNAME records to use that one instead.