Disroot-Ansible/forgejo
12
1
Fork 0
Code Pull requests Projects Releases 4 Activity

8.0.2 #57

Merged
muppeth merged 12 commits from staging into main 2024-09-03 21:01:14 +02:00
Conversation 0 Commits 12 Files changed 2 +12 -2
muppeth commented 2024-09-03 20:52:34 +02:00
Owner
Copy link
No description provided.
muppeth added 11 commits 2024-09-03 20:52:35 +02:00 
- Upgrade to version 7.0.2
- Added extra check tasks to upgrade process

Reviewed-on: #45
Reviewed-by: meaz <meaz@no-reply@disroot.org>
Co-authored-by: muppeth <muppeth@disroot.org>
Co-committed-by: muppeth <muppeth@disroot.org>
Co-authored-by: meaz <meaz@disroot.org>
Reviewed-on: #47
Reviewed-by: meaz <meaz@no-reply@disroot.org>
Co-authored-by: muppeth <muppeth@disroot.org>
Co-committed-by: muppeth <muppeth@disroot.org>
See Disroot/Disroot-Project#920

@muppeth I've just have a question about why you restart forgejo with:

```
- name: '[UPGRADE] - Restart forgejo'
  systemd:
    name: forgejo
    state: restarted
  when:
    - forgejo_is_installed.rc == 0
    - forgejo_health is defined and forgejo_health.rc is defined and forgejo_health.rc == 0

- name: '[UPGRADE] - Wait for forgejo to be back online'
  pause:
    seconds: 10
  when:
    - forgejo_is_installed.rc == 0
    - forgejo_health is defined and forgejo_health.rc is defined and forgejo_health.rc == 0
```

does forgejo need to be up to run `forgejo manager flush-queues` ?  I'm asking coz we stop forgejo just after flush.

Reviewed-on: #49
Reviewed-by: muppeth <muppeth@no-reply@disroot.org>
Co-authored-by: meaz <meaz@disroot.org>
Co-committed-by: meaz <meaz@disroot.org>
Reviewed-on: #52
Reviewed-by: muppeth <muppeth@no-reply@disroot.org>
Co-authored-by: meaz <meaz@disroot.org>
Co-committed-by: meaz <meaz@disroot.org>
Co-authored-by: meaz <meaz@disroot.org>
Reviewed-on: #53
Co-authored-by: muppeth <muppeth@disroot.org>
Co-committed-by: muppeth <muppeth@disroot.org>
security release: https://codeberg.org/forgejo/forgejo/milestone/7728

Reviewed-on: #55
Reviewed-by: meaz <meaz@no-reply@disroot.org>
Co-authored-by: muppeth <muppeth@disroot.org>
Co-committed-by: muppeth <muppeth@disroot.org>
This option set controls the provisioning options for users accessing the service via oAuth2
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#oauth2-client-oauth2_client

Reviewed-on: #56
Reviewed-by: meaz <meaz@no-reply@disroot.org>
muppeth added 1 commit 2024-09-03 20:59:55 +02:00
meaz approved these changes 2024-09-03 21:00:32 +02:00
muppeth merged commit 041aa75a0d into main 2024-09-03 21:01:14 +02:00
muppeth referenced this pull request from a commit 2024-09-03 21:01:16 +02:00
8.0.2 (#57)
Sign in to join this conversation.
Reviewers
No reviewers
meaz
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 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: Disroot-Ansible/forgejo#57
No description provided.
Delete branch "staging"

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?