Block a user
transcaffeine
pushed to transcaffeine/prepare-release at finallycoffee/nextcloud-pride-flags
2024-08-05 18:37:33 +00:00
transcaffeine
pushed tag 1.0.0-rc.0 to finallycoffee/nextcloud-pride-flags
2024-08-05 18:03:22 +00:00
transcaffeine
pushed to transcaffeine/prepare-release at finallycoffee/nextcloud-pride-flags
2024-08-05 18:00:23 +00:00
transcaffeine
pushed to transcaffeine/prepare-release at finallycoffee/nextcloud-pride-flags
2024-08-05 17:29:09 +00:00
transcaffeine
pushed to transcaffeine/prepare-release at finallycoffee/nextcloud-pride-flags
2024-08-05 16:35:59 +00:00
transcaffeine
created branch transcaffeine/prepare-release in finallycoffee/nextcloud-pride-flags
2024-08-05 16:35:59 +00:00
transcaffeine
pushed tag 0.1.0-rc.2 to finallycoffee/nextcloud-pride-flags
2024-08-05 15:04:02 +00:00
transcaffeine
pushed tag 0.1.0-rc.1 to finallycoffee/nextcloud-pride-flags
2024-08-05 14:52:54 +00:00
transcaffeine
pushed tag 0.1.0-rc.0 to finallycoffee/nextcloud-pride-flags
2024-08-05 14:37:16 +00:00
feat(roles/lego): Add support for LEGO_HTTP_PORT_FALLBACK
Where is $LEGO_HTTP_FALLBACK_PORT coming from? possibly missing documentation...
feat(roles/lego): Add support for LEGO_HTTP_PORT_FALLBACK
specify -w to avoid waiting for up to 30s. Also consider lego binds to 0.0.0.0, and a webserver might be bound only to an external IP (which would be not detected properly)
feat(roles/lego): Add support for LEGO_HTTP_PORT_FALLBACK
Move L5 directly to before its corresponding if-statement
feat(roles/lego): Add support for LEGO_HTTP_PORT_FALLBACK
Commit message scope should not include roles/, should be feat(lego): [...].