Make the per-owner project cap configurable via env
CI / php-tests (pull_request) Successful in 19s

Self-hosters shouldn't be stuck with a hardcoded 100-project limit;
MAX_PROJECTS_PER_OWNER now controls it, defaulting to 0 (unlimited).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit was merged in pull request #2.
This commit is contained in:
2026-09-05 09:34:08 +00:00
committed by aneurin
co-authored by Claude Sonnet 5
parent e59890618e
commit 16f94293ab
7 changed files with 16 additions and 6 deletions
+4
View File
@@ -25,6 +25,8 @@ final class Config
public readonly string $webauthnRpName,
/** Minimum gap between magic links sent to the same address. */
public readonly int $resendIntervalSeconds,
/** Maximum number of projects a single owner may create. 0 means unlimited. */
public readonly int $maxProjectsPerOwner,
public readonly MailConfig $mail,
) {
}
@@ -59,6 +61,7 @@ final class Config
$webauthnRpName = self::env('WEBAUTHN_RP_NAME', 'Projects');
$resendIntervalSeconds = (int) (self::env('MAGIC_LINK_RESEND_SECONDS') ?? '60');
$maxProjectsPerOwner = (int) (self::env('MAX_PROJECTS_PER_OWNER') ?? '0');
$mailLogPath = self::env('MAIL_LOG_PATH', $storagePath . '/mail.log');
if (!self::isAbsolutePath($mailLogPath)) {
@@ -87,6 +90,7 @@ final class Config
$webauthnRpId,
$webauthnRpName,
$resendIntervalSeconds,
$maxProjectsPerOwner,
$mail,
);
}