gitea/awesome-gitea
56
137
Fork 88
Code Issues 2 Pull Requests Actions Releases Activity

Add gitea Ansible role to list #117

Merged
techknowlogick merged 2 commits from solarchemist/awesome-gitea:main into main 2023-06-21 19:55:01 +00:00
Conversation 0 Commits 2 Files Changed 1 +1
solarchemist commented 2023-06-18 23:56:40 +00:00
Contributor
Copy Link

For your consideration, this PR adds an Ansible role that I've cobbled together to run two Gitea instances on the same VPS (but the logic in the role should allow an arbitrary number of instances).

It is something of a hobby project of mine, but I'd be pleased to receive any comments or suggestions on how to improve the role.

For your consideration, this PR adds an Ansible role that I've cobbled together to run two Gitea instances on the same VPS (but the logic in the role should allow an arbitrary number of instances). It is something of a hobby project of mine, but I'd be pleased to receive any comments or suggestions on how to improve the role.
solarchemist added 1 commit 2023-06-18 23:56:42 +00:00
Add gitea ansible role to list
Some checks failed
lint / lint (pull_request) Has been cancelled
Details
fe9187b00d
lunny approved these changes 2023-06-19 04:59:22 +00:00
silverwind reviewed 2023-06-19 17:21:10 +00:00
README.md Outdated
@ -145,6 +145,7 @@ A curated list of awesome projects related to Gitea.
## Scripts
- [docker-gitea](https://gitea.com/jwobith/docker-gitea) - Docker Gitea Service
- [gitea](https://codeberg.org/ansible/gitea) - Ansible role to install and configure multiple Gitea instances on the same host.
silverwind commented 2023-06-19 17:21:10 +00:00
Member
Copy Link

Call it ansible/gitea to avoid confusion?

Call it `ansible/gitea` to avoid confusion?
solarchemist commented 2023-06-19 20:42:38 +00:00
Author
Contributor
Copy Link

Thanks for pointing this out! I think you're right, listing it as simply gitea is too broad.
Although all the roles under codeberg.org/ansible/ are mine, I think ansible-gitea may also be a bit too broad.

I've never had reason to consider this before :-)
How do you like solarchemist.gitea? And which separator is de rigeur in this circumstance; dot, hyphen or slash, do you have a preference?

Thanks for pointing this out! I think you're right, listing it as simply `gitea` is too broad. Although all the roles under `codeberg.org/ansible/` are mine, I think `ansible-gitea` may also be a bit too broad. I've never had reason to consider this before :-) How do you like `solarchemist.gitea`? And which separator is *de rigeur* in this circumstance; dot, hyphen or slash, do you have a preference?
solarchemist marked this conversation as resolved
solarchemist added 1 commit 2023-06-21 11:43:14 +00:00
Renamed to give the new list addition a less confusing name.
All checks were successful
lint / lint (pull_request) Successful in 13s
Details
4bdd1d19d6
solarchemist requested review from lunny 2023-06-21 11:45:03 +00:00
jolheiser approved these changes 2023-06-21 12:13:13 +00:00
delvh approved these changes 2023-06-21 13:06:04 +00:00
techknowlogick merged commit 04fac5e4ec into main 2023-06-21 19:55:01 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
lunny
jolheiser
delvh
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/awesome-gitea#117
No description provided.
Delete Branch "solarchemist/awesome-gitea:main"

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?