improve upgrade and update to 7.0.5 #51

Merged
meaz merged 6 commits from staging into main 2024-08-06 21:23:23 +02:00

6 commits

Author SHA1 Message Date
b729a6e5cf
Merge branch 'main' into staging 2024-08-06 21:22:45 +02:00
bc971d10bb exclude .min.css from being copy + include css files that don't start with theme in there name! (#52)
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>
2024-07-30 18:21:56 +02:00
4690ef208e improve upgrade and update to 7.0.5 (#49)
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>
2024-07-15 18:36:23 +02:00
538d530f51
Merge branch 'main' into staging 2024-07-09 20:42:40 +02:00
1e84bbe2e9 V7.0.4 (#47)
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>
2024-06-15 14:52:48 +02:00
5e5c8dd415 V7.0.2 (#45)
- 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>
2024-06-11 00:47:32 +02:00