diff --git a/export/config/app.php b/export/config/app.php deleted file mode 100644 index 47c3359c..00000000 --- a/export/config/app.php +++ /dev/null @@ -1,126 +0,0 @@ - env('APP_NAME', 'Statamic'), - - /* - |-------------------------------------------------------------------------- - | Application Environment - |-------------------------------------------------------------------------- - | - | This value determines the "environment" your application is currently - | running in. This may determine how you prefer to configure various - | services the application utilizes. Set this in your ".env" file. - | - */ - - 'env' => env('APP_ENV', 'production'), - - /* - |-------------------------------------------------------------------------- - | Application Debug Mode - |-------------------------------------------------------------------------- - | - | When your application is in debug mode, detailed error messages with - | stack traces will be shown on every error that occurs within your - | application. If disabled, a simple generic error page is shown. - | - */ - - 'debug' => (bool) env('APP_DEBUG', false), - - /* - |-------------------------------------------------------------------------- - | Application URL - |-------------------------------------------------------------------------- - | - | This URL is used by the console to properly generate URLs when using - | the Artisan command line tool. You should set this to the root of - | the application so that it's available within Artisan commands. - | - */ - - 'url' => env('APP_URL', 'http://localhost'), - - /* - |-------------------------------------------------------------------------- - | Application Timezone - |-------------------------------------------------------------------------- - | - | Here you may specify the default timezone for your application, which - | will be used by the PHP date and date-time functions. The timezone - | is set to "UTC" by default as it is suitable for most use cases. - | - */ - - 'timezone' => 'UTC', - - /* - |-------------------------------------------------------------------------- - | Application Locale Configuration - |-------------------------------------------------------------------------- - | - | The application locale determines the default locale that will be used - | by Laravel's translation / localization methods. This option can be - | set to any locale for which you plan to have translation strings. - | - */ - - 'locale' => env('APP_LOCALE', 'en'), - - 'fallback_locale' => env('APP_FALLBACK_LOCALE', 'en'), - - 'faker_locale' => env('APP_FAKER_LOCALE', 'en_US'), - - /* - |-------------------------------------------------------------------------- - | Encryption Key - |-------------------------------------------------------------------------- - | - | This key is utilized by Laravel's encryption services and should be set - | to a random, 32 character string to ensure that all encrypted values - | are secure. You should do this prior to deploying the application. - | - */ - - 'cipher' => 'AES-256-CBC', - - 'key' => env('APP_KEY'), - - 'previous_keys' => [ - ...array_filter( - explode(',', (string) env('APP_PREVIOUS_KEYS', '')) - ), - ], - - /* - |-------------------------------------------------------------------------- - | Maintenance Mode Driver - |-------------------------------------------------------------------------- - | - | These configuration options determine the driver used to determine and - | manage Laravel's "maintenance mode" status. The "cache" driver will - | allow maintenance mode to be controlled across multiple machines. - | - | Supported drivers: "file", "cache" - | - */ - - 'maintenance' => [ - 'driver' => env('APP_MAINTENANCE_DRIVER', 'file'), - 'store' => env('APP_MAINTENANCE_STORE', 'file'), - ], - -]; diff --git a/export/config/auth.php b/export/config/auth.php deleted file mode 100644 index 8e3bb617..00000000 --- a/export/config/auth.php +++ /dev/null @@ -1,126 +0,0 @@ - [ - 'guard' => env('AUTH_GUARD', 'web'), - 'passwords' => env('AUTH_PASSWORD_BROKER', 'users'), - ], - - /* - |-------------------------------------------------------------------------- - | Authentication Guards - |-------------------------------------------------------------------------- - | - | Next, you may define every authentication guard for your application. - | Of course, a great default configuration has been defined for you - | which utilizes session storage plus the Eloquent user provider. - | - | All authentication guards have a user provider, which defines how the - | users are actually retrieved out of your database or other storage - | system used by the application. Typically, Eloquent is utilized. - | - | Supported: "session" - | - */ - - 'guards' => [ - 'web' => [ - 'driver' => 'session', - 'provider' => 'users', - ], - ], - - /* - |-------------------------------------------------------------------------- - | User Providers - |-------------------------------------------------------------------------- - | - | All authentication guards have a user provider, which defines how the - | users are actually retrieved out of your database or other storage - | system used by the application. Typically, Eloquent is utilized. - | - | If you have multiple user tables or models you may configure multiple - | providers to represent the model / table. These providers may then - | be assigned to any extra authentication guards you have defined. - | - | Supported: "statamic", "database", "eloquent" - | - */ - - 'providers' => [ - 'users' => [ - 'driver' => 'statamic', - ], - - // 'users' => [ - // 'driver' => 'eloquent', - // 'model' => env('AUTH_MODEL', App\Models\User::class), - // ], - - // 'users' => [ - // 'driver' => 'database', - // 'table' => 'users', - // ], - ], - - /* - |-------------------------------------------------------------------------- - | Resetting Passwords - |-------------------------------------------------------------------------- - | - | These configuration options specify the behavior of Laravel's password - | reset functionality, including the table utilized for token storage - | and the user provider that is invoked to actually retrieve users. - | - | The expiry time is the number of minutes that each reset token will be - | considered valid. This security feature keeps tokens short-lived so - | they have less time to be guessed. You may change this as needed. - | - | The throttle setting is the number of seconds a user must wait before - | generating more password reset tokens. This prevents the user from - | quickly generating a very large amount of password reset tokens. - | - */ - - 'passwords' => [ - 'users' => [ - 'provider' => 'users', - 'table' => env('AUTH_PASSWORD_RESET_TOKEN_TABLE', 'password_reset_tokens'), - 'expire' => 60, - 'throttle' => 60, - ], - - 'activations' => [ - 'provider' => 'users', - 'table' => env('AUTH_ACTIVATION_TOKEN_TABLE', 'password_activation_tokens'), - 'expire' => 4320, - 'throttle' => 60, - ], - ], - - /* - |-------------------------------------------------------------------------- - | Password Confirmation Timeout - |-------------------------------------------------------------------------- - | - | Here you may define the number of seconds before a password confirmation - | window expires and users are asked to re-enter their password via the - | confirmation screen. By default, the timeout lasts for three hours. - | - */ - - 'password_timeout' => env('AUTH_PASSWORD_TIMEOUT', 10800), - -]; diff --git a/export/config/cache.php b/export/config/cache.php deleted file mode 100644 index e7b42f29..00000000 --- a/export/config/cache.php +++ /dev/null @@ -1,122 +0,0 @@ - env('CACHE_STORE', 'file'), - - /* - |-------------------------------------------------------------------------- - | Cache Stores - |-------------------------------------------------------------------------- - | - | Here you may define all of the cache "stores" for your application as - | well as their drivers. You may even define multiple stores for the - | same cache driver to group types of items stored in your caches. - | - | Supported drivers: "array", "database", "file", "memcached", - | "redis", "dynamodb", "octane", - | "failover", "null" - | - */ - - 'stores' => [ - - 'array' => [ - 'driver' => 'array', - 'serialize' => false, - ], - - 'database' => [ - 'driver' => 'database', - 'connection' => env('DB_CACHE_CONNECTION', null), - 'table' => env('DB_CACHE_TABLE', 'cache'), - 'lock_connection' => env('DB_CACHE_LOCK_CONNECTION'), - 'lock_table' => env('DB_CACHE_LOCK_TABLE'), - ], - - 'file' => [ - 'driver' => 'file', - 'path' => storage_path('framework/cache/data'), - 'lock_path' => storage_path('framework/cache/data'), - ], - - 'memcached' => [ - 'driver' => 'memcached', - 'persistent_id' => env('MEMCACHED_PERSISTENT_ID'), - 'sasl' => [ - env('MEMCACHED_USERNAME'), - env('MEMCACHED_PASSWORD'), - ], - 'options' => [ - // Memcached::OPT_CONNECT_TIMEOUT => 2000, - ], - 'servers' => [ - [ - 'host' => env('MEMCACHED_HOST', '127.0.0.1'), - 'port' => env('MEMCACHED_PORT', 11211), - 'weight' => 100, - ], - ], - ], - - 'redis' => [ - 'driver' => 'redis', - 'connection' => env('REDIS_CACHE_CONNECTION', 'cache'), - 'lock_connection' => env('REDIS_CACHE_LOCK_CONNECTION', 'default'), - ], - - 'dynamodb' => [ - 'driver' => 'dynamodb', - 'key' => env('AWS_ACCESS_KEY_ID'), - 'secret' => env('AWS_SECRET_ACCESS_KEY'), - 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), - 'table' => env('DYNAMODB_CACHE_TABLE', 'cache'), - 'endpoint' => env('DYNAMODB_ENDPOINT'), - ], - - 'octane' => [ - 'driver' => 'octane', - ], - - 'failover' => [ - 'driver' => 'failover', - 'stores' => [ - 'database', - 'array', - ], - ], - - 'static_cache' => [ - 'driver' => 'file', - 'path' => storage_path('statamic/static-urls-cache'), - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Cache Key Prefix - |-------------------------------------------------------------------------- - | - | When utilizing the APC, database, memcached, Redis, and DynamoDB cache - | stores, there might be other applications using the same cache. For - | that reason, you may prefix every cache key to avoid collisions. - | - */ - - 'prefix' => env('CACHE_PREFIX', Str::slug((string) env('APP_NAME', 'laravel')).'-cache-'), - -]; diff --git a/export/config/database.php b/export/config/database.php deleted file mode 100644 index df933e7f..00000000 --- a/export/config/database.php +++ /dev/null @@ -1,183 +0,0 @@ - env('DB_CONNECTION', 'sqlite'), - - /* - |-------------------------------------------------------------------------- - | Database Connections - |-------------------------------------------------------------------------- - | - | Below are all of the database connections defined for your application. - | An example configuration is provided for each database system which - | is supported by Laravel. You're free to add / remove connections. - | - */ - - 'connections' => [ - - 'sqlite' => [ - 'driver' => 'sqlite', - 'url' => env('DB_URL'), - 'database' => env('DB_DATABASE', database_path('database.sqlite')), - 'prefix' => '', - 'foreign_key_constraints' => env('DB_FOREIGN_KEYS', true), - 'busy_timeout' => null, - 'journal_mode' => null, - 'synchronous' => null, - 'transaction_mode' => 'DEFERRED', - ], - - 'mysql' => [ - 'driver' => 'mysql', - 'url' => env('DB_URL'), - 'host' => env('DB_HOST', '127.0.0.1'), - 'port' => env('DB_PORT', '3306'), - 'database' => env('DB_DATABASE', 'laravel'), - 'username' => env('DB_USERNAME', 'root'), - 'password' => env('DB_PASSWORD', ''), - 'unix_socket' => env('DB_SOCKET', ''), - 'charset' => env('DB_CHARSET', 'utf8mb4'), - 'collation' => env('DB_COLLATION', 'utf8mb4_unicode_ci'), - 'prefix' => '', - 'prefix_indexes' => true, - 'strict' => true, - 'engine' => null, - 'options' => extension_loaded('pdo_mysql') ? array_filter([ - (PHP_VERSION_ID >= 80500 ? \Pdo\Mysql::ATTR_SSL_CA : \PDO::MYSQL_ATTR_SSL_CA) => env('MYSQL_ATTR_SSL_CA'), - ]) : [], - ], - - 'mariadb' => [ - 'driver' => 'mariadb', - 'url' => env('DB_URL'), - 'host' => env('DB_HOST', '127.0.0.1'), - 'port' => env('DB_PORT', '3306'), - 'database' => env('DB_DATABASE', 'laravel'), - 'username' => env('DB_USERNAME', 'root'), - 'password' => env('DB_PASSWORD', ''), - 'unix_socket' => env('DB_SOCKET', ''), - 'charset' => env('DB_CHARSET', 'utf8mb4'), - 'collation' => env('DB_COLLATION', 'utf8mb4_unicode_ci'), - 'prefix' => '', - 'prefix_indexes' => true, - 'strict' => true, - 'engine' => null, - 'options' => extension_loaded('pdo_mysql') ? array_filter([ - (PHP_VERSION_ID >= 80500 ? \Pdo\Mysql::ATTR_SSL_CA : \PDO::MYSQL_ATTR_SSL_CA) => env('MYSQL_ATTR_SSL_CA'), - ]) : [], - ], - - 'pgsql' => [ - 'driver' => 'pgsql', - 'url' => env('DB_URL'), - 'host' => env('DB_HOST', '127.0.0.1'), - 'port' => env('DB_PORT', '5432'), - 'database' => env('DB_DATABASE', 'laravel'), - 'username' => env('DB_USERNAME', 'root'), - 'password' => env('DB_PASSWORD', ''), - 'charset' => env('DB_CHARSET', 'utf8'), - 'prefix' => '', - 'prefix_indexes' => true, - 'search_path' => 'public', - 'sslmode' => env('DB_SSLMODE', 'prefer'), - ], - - 'sqlsrv' => [ - 'driver' => 'sqlsrv', - 'url' => env('DB_URL'), - 'host' => env('DB_HOST', 'localhost'), - 'port' => env('DB_PORT', '1433'), - 'database' => env('DB_DATABASE', 'laravel'), - 'username' => env('DB_USERNAME', 'root'), - 'password' => env('DB_PASSWORD', ''), - 'charset' => env('DB_CHARSET', 'utf8'), - 'prefix' => '', - 'prefix_indexes' => true, - // 'encrypt' => env('DB_ENCRYPT', 'yes'), - // 'trust_server_certificate' => env('DB_TRUST_SERVER_CERTIFICATE', 'false'), - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Migration Repository Table - |-------------------------------------------------------------------------- - | - | This table keeps track of all the migrations that have already run for - | your application. Using this information, we can determine which of - | the migrations on disk haven't actually been run on the database. - | - */ - - 'migrations' => [ - 'table' => 'migrations', - 'update_date_on_publish' => true, - ], - - /* - |-------------------------------------------------------------------------- - | Redis Databases - |-------------------------------------------------------------------------- - | - | Redis is an open source, fast, and advanced key-value store that also - | provides a richer body of commands than a typical key-value system - | such as Memcached. You may define your connection settings here. - | - */ - - 'redis' => [ - - 'client' => env('REDIS_CLIENT', 'phpredis'), - - 'options' => [ - 'cluster' => env('REDIS_CLUSTER', 'redis'), - 'prefix' => env('REDIS_PREFIX', Str::slug((string) env('APP_NAME', 'laravel')).'-database-'), - 'persistent' => env('REDIS_PERSISTENT', false), - ], - - 'default' => [ - 'url' => env('REDIS_URL'), - 'host' => env('REDIS_HOST', '127.0.0.1'), - 'username' => env('REDIS_USERNAME'), - 'password' => env('REDIS_PASSWORD'), - 'port' => env('REDIS_PORT', '6379'), - 'database' => env('REDIS_DB', '0'), - 'max_retries' => env('REDIS_MAX_RETRIES', 3), - 'backoff_algorithm' => env('REDIS_BACKOFF_ALGORITHM', 'decorrelated_jitter'), - 'backoff_base' => env('REDIS_BACKOFF_BASE', 100), - 'backoff_cap' => env('REDIS_BACKOFF_CAP', 1000), - ], - - 'cache' => [ - 'url' => env('REDIS_URL'), - 'host' => env('REDIS_HOST', '127.0.0.1'), - 'username' => env('REDIS_USERNAME'), - 'password' => env('REDIS_PASSWORD'), - 'port' => env('REDIS_PORT', '6379'), - 'database' => env('REDIS_CACHE_DB', '1'), - 'max_retries' => env('REDIS_MAX_RETRIES', 3), - 'backoff_algorithm' => env('REDIS_BACKOFF_ALGORITHM', 'decorrelated_jitter'), - 'backoff_base' => env('REDIS_BACKOFF_BASE', 100), - 'backoff_cap' => env('REDIS_BACKOFF_CAP', 1000), - ], - - ], - -]; diff --git a/export/config/dok.php b/export/config/dok.php deleted file mode 100644 index 12bcd412..00000000 --- a/export/config/dok.php +++ /dev/null @@ -1,135 +0,0 @@ - [ - - /* - |-------------------------------------------------------------------------- - | Component Bindings - |-------------------------------------------------------------------------- - | - | You can bind CommonMark container blocks to Laravel components here. - | Read more about Component Binding in the Dok documentation. - | - */ - - 'components' => [ - 'note' => ['template' => 'components.hint.hint'], - 'tip' => ['template' => 'components.hint.hint'], - 'important' => ['template' => 'components.hint.hint'], - 'caution' => ['template' => 'components.hint.hint'], - 'warning' => ['template' => 'components.hint.hint'], - - 'lead' => [ - 'template' => 'components.lead.lead', - ], - - 'card' => [ - 'template' => 'components.card.card', - 'slots' => ['cta-text'], - ], - 'cardgroup' => [ - 'template' => 'components.card-group.card-group', - ], - 'accordion' => [ - 'template' => 'components.accordion.accordion', - ], - ], - - /* - |-------------------------------------------------------------------------- - | Torchlight Options - |-------------------------------------------------------------------------- - | - | If you enabled Torchlight for syntax highlighting when installing - | the starterkit, you can update the options for that here. - | - */ - - 'torchlight' => [ - 'enabled' => env('TORCHLIGHT_ENABLED', true), - - 'theme' => env('TORCHLIGHT_THEME', 'olaolu-palenight'), - - 'options' => [ - 'lineNumbers' => false, - 'lineNumbersStart' => 1, - 'lineNumberAndDiffIndicatorRightPadding' => 2, - ], - ], - ], - - /* - |-------------------------------------------------------------------------- - | Resources - |-------------------------------------------------------------------------- - | - | If you're using Github to sync your content, you can add your resources - | here. - | - */ - - 'resources' => [ - 'dok-docs' => [ - 'source' => 'github', - 'repo' => 'jonkaric/dok-docs', - 'branch' => 'main', - 'content' => ['dok', 'tok', 'bok'], - 'token' => env('GITHUB_SYNC'), - ], - 'documentation_v2_content' => [ - 'repo' => 'jonkaric/dok-docs', - 'branch' => 'main', - 'branch' => 'main', - 'token' => env('GITHUB_SYNC_TOKEN_DOK_DOCS'), - ], - 'documentation_v2_all' => [ - 'repo' => 'fawnsoftware/dok-docs', - 'branch' => 'main', - 'token' => env('GITHUB_SYNC_TOKEN_DOK_DOCS'), - ], - ], - - /* - |-------------------------------------------------------------------------- - | Resource Location - |-------------------------------------------------------------------------- - | - | When syncing your resources from GitHub or other providers, you can - | choose where on your filesystem the files should live. This should - | be relative to the root of your project, as methods that use this - | config use base_path under the hood. - | - */ - - 'resource_location' => base_path('content/docs'), - - /* - |-------------------------------------------------------------------------- - | Create Routes - |-------------------------------------------------------------------------- - | - | When creating a new release you will get to pick which route you want - | to use. You can customise that list here by adding more options - | or commenting out ones you do not wish to use. - | - | You can always customise the release route later in the - | collection settings, under routes. - | - | will be replaced with the slugified name of your project. - | will be replaced with the slugified version of the release. - | - | The key is the route that will be used. - | The value is the human-friendly name. - | - */ - 'create_routes' => [ - "{{ !parent_uri ?= '/' }}{{ parent_uri }}/{{ slug }}" => '/...', - "{{ !parent_uri ?= '//' }}{{ parent_uri }}/{{ slug }}" => '//...', - "{{ !parent_uri ?= 'docs/' }}{{ parent_uri }}/{{ slug }}" => 'docs/...', - "{{ !parent_uri ?= 'docs//' }}{{ parent_uri }}/{{ slug }}" => 'docs//...', - "{{ !parent_uri ?= 'docs///' }}{{ parent_uri }}/{{ slug }}" => 'docs///...', - '{{ parent_uri }}/{{ slug }}' => '/...', - ], -]; diff --git a/export/config/filesystems.php b/export/config/filesystems.php deleted file mode 100644 index cb340593..00000000 --- a/export/config/filesystems.php +++ /dev/null @@ -1,90 +0,0 @@ - env('FILESYSTEM_DISK', 'local'), - - /* - |-------------------------------------------------------------------------- - | Filesystem Disks - |-------------------------------------------------------------------------- - | - | Below you may configure as many filesystem disks as necessary, and you - | may even configure multiple disks for the same driver. Examples for - | most supported storage drivers are configured here for reference. - | - | Supported drivers: "local", "ftp", "sftp", "s3" - | - */ - - 'disks' => [ - - 'local' => [ - 'driver' => 'local', - 'root' => storage_path('app/private'), - 'serve' => true, - 'throw' => false, - 'report' => false, - ], - - 'public' => [ - 'driver' => 'local', - 'root' => storage_path('app/public'), - 'url' => rtrim(env('APP_URL'), '/').'/storage', - 'visibility' => 'public', - 'throw' => false, - 'report' => false, - ], - - 's3' => [ - 'driver' => 's3', - 'key' => env('AWS_ACCESS_KEY_ID'), - 'secret' => env('AWS_SECRET_ACCESS_KEY'), - 'region' => env('AWS_DEFAULT_REGION'), - 'bucket' => env('AWS_BUCKET'), - 'url' => env('AWS_URL'), - 'endpoint' => env('AWS_ENDPOINT'), - 'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', false), - 'throw' => false, - 'report' => false, - // 'visibility' => 'public', // https://statamic.dev/assets#container-visibility - ], - - 'assets' => [ - 'driver' => 'local', - 'root' => public_path('assets'), - 'url' => '/assets', - 'visibility' => 'public', - 'throw' => false, - 'report' => false, - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Symbolic Links - |-------------------------------------------------------------------------- - | - | Here you may configure the symbolic links that will be created when the - | `storage:link` Artisan command is executed. The array keys should be - | the locations of the links and the values should be their targets. - | - */ - - 'links' => [ - public_path('storage') => storage_path('app/public'), - ], - -]; diff --git a/export/config/logging.php b/export/config/logging.php deleted file mode 100644 index 9e998a49..00000000 --- a/export/config/logging.php +++ /dev/null @@ -1,132 +0,0 @@ - env('LOG_CHANNEL', 'stack'), - - /* - |-------------------------------------------------------------------------- - | Deprecations Log Channel - |-------------------------------------------------------------------------- - | - | This option controls the log channel that should be used to log warnings - | regarding deprecated PHP and library features. This allows you to get - | your application ready for upcoming major versions of dependencies. - | - */ - - 'deprecations' => [ - 'channel' => env('LOG_DEPRECATIONS_CHANNEL', 'null'), - 'trace' => env('LOG_DEPRECATIONS_TRACE', false), - ], - - /* - |-------------------------------------------------------------------------- - | Log Channels - |-------------------------------------------------------------------------- - | - | Here you may configure the log channels for your application. Laravel - | utilizes the Monolog PHP logging library, which includes a variety - | of powerful log handlers and formatters that you're free to use. - | - | Available drivers: "single", "daily", "slack", "syslog", - | "errorlog", "monolog", "custom", "stack" - | - */ - - 'channels' => [ - - 'stack' => [ - 'driver' => 'stack', - 'channels' => explode(',', (string) env('LOG_STACK', 'single')), - 'ignore_exceptions' => false, - ], - - 'single' => [ - 'driver' => 'single', - 'path' => storage_path('logs/laravel.log'), - 'level' => env('LOG_LEVEL', 'debug'), - 'replace_placeholders' => true, - ], - - 'daily' => [ - 'driver' => 'daily', - 'path' => storage_path('logs/laravel.log'), - 'level' => env('LOG_LEVEL', 'debug'), - 'days' => env('LOG_DAILY_DAYS', 14), - 'replace_placeholders' => true, - ], - - 'slack' => [ - 'driver' => 'slack', - 'url' => env('LOG_SLACK_WEBHOOK_URL'), - 'username' => env('LOG_SLACK_USERNAME', 'Laravel Log'), - 'emoji' => env('LOG_SLACK_EMOJI', ':boom:'), - 'level' => env('LOG_LEVEL', 'critical'), - 'replace_placeholders' => true, - ], - - 'papertrail' => [ - 'driver' => 'monolog', - 'level' => env('LOG_LEVEL', 'debug'), - 'handler' => env('LOG_PAPERTRAIL_HANDLER', SyslogUdpHandler::class), - 'handler_with' => [ - 'host' => env('PAPERTRAIL_URL'), - 'port' => env('PAPERTRAIL_PORT'), - 'connectionString' => 'tls://'.env('PAPERTRAIL_URL').':'.env('PAPERTRAIL_PORT'), - ], - 'processors' => [PsrLogMessageProcessor::class], - ], - - 'stderr' => [ - 'driver' => 'monolog', - 'level' => env('LOG_LEVEL', 'debug'), - 'handler' => StreamHandler::class, - 'handler_with' => [ - 'stream' => 'php://stderr', - ], - 'formatter' => env('LOG_STDERR_FORMATTER'), - 'processors' => [PsrLogMessageProcessor::class], - ], - - 'syslog' => [ - 'driver' => 'syslog', - 'level' => env('LOG_LEVEL', 'debug'), - 'facility' => env('LOG_SYSLOG_FACILITY', LOG_USER), - 'replace_placeholders' => true, - ], - - 'errorlog' => [ - 'driver' => 'errorlog', - 'level' => env('LOG_LEVEL', 'debug'), - 'replace_placeholders' => true, - ], - - 'null' => [ - 'driver' => 'monolog', - 'handler' => NullHandler::class, - ], - - 'emergency' => [ - 'path' => storage_path('logs/laravel.log'), - ], - - ], - -]; diff --git a/export/config/mail.php b/export/config/mail.php deleted file mode 100644 index 522b284b..00000000 --- a/export/config/mail.php +++ /dev/null @@ -1,118 +0,0 @@ - env('MAIL_MAILER', 'log'), - - /* - |-------------------------------------------------------------------------- - | Mailer Configurations - |-------------------------------------------------------------------------- - | - | Here you may configure all of the mailers used by your application plus - | their respective settings. Several examples have been configured for - | you and you are free to add your own as your application requires. - | - | Laravel supports a variety of mail "transport" drivers that can be used - | when delivering an email. You may specify which one you're using for - | your mailers below. You may also add additional mailers if needed. - | - | Supported: "smtp", "sendmail", "mailgun", "ses", "ses-v2", - | "postmark", "resend", "log", "array", - | "failover", "roundrobin" - | - */ - - 'mailers' => [ - - 'smtp' => [ - 'transport' => 'smtp', - 'scheme' => env('MAIL_SCHEME'), - 'url' => env('MAIL_URL'), - 'host' => env('MAIL_HOST', '127.0.0.1'), - 'port' => env('MAIL_PORT', 2525), - 'username' => env('MAIL_USERNAME'), - 'password' => env('MAIL_PASSWORD'), - 'timeout' => null, - 'local_domain' => env('MAIL_EHLO_DOMAIN', parse_url((string) env('APP_URL', 'http://localhost'), PHP_URL_HOST)), - ], - - 'ses' => [ - 'transport' => 'ses', - ], - - 'postmark' => [ - 'transport' => 'postmark', - // 'message_stream_id' => env('POSTMARK_MESSAGE_STREAM_ID'), - // 'client' => [ - // 'timeout' => 5, - // ], - ], - - 'resend' => [ - 'transport' => 'resend', - ], - - 'sendmail' => [ - 'transport' => 'sendmail', - 'path' => env('MAIL_SENDMAIL_PATH', '/usr/sbin/sendmail -bs -i'), - ], - - 'log' => [ - 'transport' => 'log', - 'channel' => env('MAIL_LOG_CHANNEL'), - ], - - 'array' => [ - 'transport' => 'array', - ], - - 'failover' => [ - 'transport' => 'failover', - 'mailers' => [ - 'smtp', - 'log', - ], - 'retry_after' => 60, - ], - - 'roundrobin' => [ - 'transport' => 'roundrobin', - 'mailers' => [ - 'ses', - 'postmark', - ], - 'retry_after' => 60, - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Global "From" Address - |-------------------------------------------------------------------------- - | - | You may wish for all emails sent by your application to be sent from - | the same address. Here you may specify a name and address that is - | used globally for all emails that are sent by your application. - | - */ - - 'from' => [ - 'address' => env('MAIL_FROM_ADDRESS', 'hello@example.com'), - 'name' => env('MAIL_FROM_NAME', 'Example'), - ], - -]; diff --git a/export/config/queue.php b/export/config/queue.php deleted file mode 100644 index d0e0f50e..00000000 --- a/export/config/queue.php +++ /dev/null @@ -1,129 +0,0 @@ - env('QUEUE_CONNECTION', 'sync'), - - /* - |-------------------------------------------------------------------------- - | Queue Connections - |-------------------------------------------------------------------------- - | - | Here you may configure the connection options for every queue backend - | used by your application. An example configuration is provided for - | each backend supported by Laravel. You're also free to add more. - | - | Drivers: "sync", "database", "beanstalkd", "sqs", "redis", - | "deferred", "background", "failover", "null" - | - */ - - 'connections' => [ - - 'sync' => [ - 'driver' => 'sync', - ], - - 'database' => [ - 'driver' => 'database', - 'connection' => env('DB_QUEUE_CONNECTION'), - 'table' => env('DB_QUEUE_TABLE', 'jobs'), - 'queue' => env('DB_QUEUE', 'default'), - 'retry_after' => (int) env('DB_QUEUE_RETRY_AFTER', 90), - 'after_commit' => false, - ], - - 'beanstalkd' => [ - 'driver' => 'beanstalkd', - 'host' => env('BEANSTALKD_QUEUE_HOST', 'localhost'), - 'queue' => env('BEANSTALKD_QUEUE', 'default'), - 'retry_after' => (int) env('BEANSTALKD_QUEUE_RETRY_AFTER', 90), - 'block_for' => 0, - 'after_commit' => false, - ], - - 'sqs' => [ - 'driver' => 'sqs', - 'key' => env('AWS_ACCESS_KEY_ID'), - 'secret' => env('AWS_SECRET_ACCESS_KEY'), - 'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'), - 'queue' => env('SQS_QUEUE', 'default'), - 'suffix' => env('SQS_SUFFIX'), - 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), - 'after_commit' => false, - ], - - 'redis' => [ - 'driver' => 'redis', - 'connection' => env('REDIS_QUEUE_CONNECTION', 'default'), - 'queue' => env('REDIS_QUEUE', 'default'), - 'retry_after' => (int) env('REDIS_QUEUE_RETRY_AFTER', 90), - 'block_for' => null, - 'after_commit' => false, - ], - - 'deferred' => [ - 'driver' => 'deferred', - ], - - 'background' => [ - 'driver' => 'background', - ], - - 'failover' => [ - 'driver' => 'failover', - 'connections' => [ - 'database', - 'deferred', - ], - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Job Batching - |-------------------------------------------------------------------------- - | - | The following options configure the database and table that store job - | batching information. These options can be updated to any database - | connection and table which has been defined by your application. - | - */ - - 'batching' => [ - 'database' => env('DB_CONNECTION', 'sqlite'), - 'table' => 'job_batches', - ], - - /* - |-------------------------------------------------------------------------- - | Failed Queue Jobs - |-------------------------------------------------------------------------- - | - | These options configure the behavior of failed queue job logging so you - | can control how and where failed jobs are stored. Laravel ships with - | support for storing failed jobs in a simple file or in a database. - | - | Supported drivers: "database-uuids", "dynamodb", "file", "null" - | - */ - - 'failed' => [ - 'driver' => env('QUEUE_FAILED_DRIVER', 'database-uuids'), - 'database' => env('DB_CONNECTION', 'sqlite'), - 'table' => 'failed_jobs', - ], - -]; diff --git a/export/config/services.php b/export/config/services.php deleted file mode 100644 index 6a90eb83..00000000 --- a/export/config/services.php +++ /dev/null @@ -1,38 +0,0 @@ - [ - 'key' => env('POSTMARK_API_KEY'), - ], - - 'resend' => [ - 'key' => env('RESEND_API_KEY'), - ], - - 'ses' => [ - 'key' => env('AWS_ACCESS_KEY_ID'), - 'secret' => env('AWS_SECRET_ACCESS_KEY'), - 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), - ], - - 'slack' => [ - 'notifications' => [ - 'bot_user_oauth_token' => env('SLACK_BOT_USER_OAUTH_TOKEN'), - 'channel' => env('SLACK_BOT_USER_DEFAULT_CHANNEL'), - ], - ], - -]; diff --git a/export/config/session.php b/export/config/session.php deleted file mode 100644 index e6197a0f..00000000 --- a/export/config/session.php +++ /dev/null @@ -1,217 +0,0 @@ - env('SESSION_DRIVER', 'file'), - - /* - |-------------------------------------------------------------------------- - | Session Lifetime - |-------------------------------------------------------------------------- - | - | Here you may specify the number of minutes that you wish the session - | to be allowed to remain idle before it expires. If you want them - | to expire immediately when the browser is closed then you may - | indicate that via the expire_on_close configuration option. - | - */ - - 'lifetime' => (int) env('SESSION_LIFETIME', 120), - - 'expire_on_close' => env('SESSION_EXPIRE_ON_CLOSE', false), - - /* - |-------------------------------------------------------------------------- - | Session Encryption - |-------------------------------------------------------------------------- - | - | This option allows you to easily specify that all of your session data - | should be encrypted before it's stored. All encryption is performed - | automatically by Laravel and you may use the session like normal. - | - */ - - 'encrypt' => env('SESSION_ENCRYPT', false), - - /* - |-------------------------------------------------------------------------- - | Session File Location - |-------------------------------------------------------------------------- - | - | When utilizing the "file" session driver, the session files are placed - | on disk. The default storage location is defined here; however, you - | are free to provide another location where they should be stored. - | - */ - - 'files' => storage_path('framework/sessions'), - - /* - |-------------------------------------------------------------------------- - | Session Database Connection - |-------------------------------------------------------------------------- - | - | When using the "database" or "redis" session drivers, you may specify a - | connection that should be used to manage these sessions. This should - | correspond to a connection in your database configuration options. - | - */ - - 'connection' => env('SESSION_CONNECTION'), - - /* - |-------------------------------------------------------------------------- - | Session Database Table - |-------------------------------------------------------------------------- - | - | When using the "database" session driver, you may specify the table to - | be used to store sessions. Of course, a sensible default is defined - | for you; however, you're welcome to change this to another table. - | - */ - - 'table' => env('SESSION_TABLE', 'sessions'), - - /* - |-------------------------------------------------------------------------- - | Session Cache Store - |-------------------------------------------------------------------------- - | - | When using one of the framework's cache driven session backends, you may - | define the cache store which should be used to store the session data - | between requests. This must match one of your defined cache stores. - | - | Affects: "dynamodb", "memcached", "redis" - | - */ - - 'store' => env('SESSION_STORE'), - - /* - |-------------------------------------------------------------------------- - | Session Sweeping Lottery - |-------------------------------------------------------------------------- - | - | Some session drivers must manually sweep their storage location to get - | rid of old sessions from storage. Here are the chances that it will - | happen on a given request. By default, the odds are 2 out of 100. - | - */ - - 'lottery' => [2, 100], - - /* - |-------------------------------------------------------------------------- - | Session Cookie Name - |-------------------------------------------------------------------------- - | - | Here you may change the name of the session cookie that is created by - | the framework. Typically, you should not need to change this value - | since doing so does not grant a meaningful security improvement. - | - */ - - 'cookie' => env( - 'SESSION_COOKIE', - Str::slug((string) env('APP_NAME', 'laravel')).'-session' - ), - - /* - |-------------------------------------------------------------------------- - | Session Cookie Path - |-------------------------------------------------------------------------- - | - | The session cookie path determines the path for which the cookie will - | be regarded as available. Typically, this will be the root path of - | your application, but you're free to change this when necessary. - | - */ - - 'path' => env('SESSION_PATH', '/'), - - /* - |-------------------------------------------------------------------------- - | Session Cookie Domain - |-------------------------------------------------------------------------- - | - | This value determines the domain and subdomains the session cookie is - | available to. By default, the cookie will be available to the root - | domain without subdomains. Typically, this shouldn't be changed. - | - */ - - 'domain' => env('SESSION_DOMAIN'), - - /* - |-------------------------------------------------------------------------- - | HTTPS Only Cookies - |-------------------------------------------------------------------------- - | - | By setting this option to true, session cookies will only be sent back - | to the server if the browser has a HTTPS connection. This will keep - | the cookie from being sent to you when it can't be done securely. - | - */ - - 'secure' => env('SESSION_SECURE_COOKIE'), - - /* - |-------------------------------------------------------------------------- - | HTTP Access Only - |-------------------------------------------------------------------------- - | - | Setting this value to true will prevent JavaScript from accessing the - | value of the cookie and the cookie will only be accessible through - | the HTTP protocol. It's unlikely you should disable this option. - | - */ - - 'http_only' => env('SESSION_HTTP_ONLY', true), - - /* - |-------------------------------------------------------------------------- - | Same-Site Cookies - |-------------------------------------------------------------------------- - | - | This option determines how your cookies behave when cross-site requests - | take place, and can be used to mitigate CSRF attacks. By default, we - | will set this value to "lax" to permit secure cross-site requests. - | - | See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value - | - | Supported: "lax", "strict", "none", null - | - */ - - 'same_site' => env('SESSION_SAME_SITE', 'lax'), - - /* - |-------------------------------------------------------------------------- - | Partitioned Cookies - |-------------------------------------------------------------------------- - | - | Setting this value to true will tie the cookie to the top-level site for - | a cross-site context. Partitioned cookies are accepted by the browser - | when flagged "secure" and the Same-Site attribute is set to "none". - | - */ - - 'partitioned' => env('SESSION_PARTITIONED_COOKIE', false), - -]; diff --git a/export/config/statamic/antlers.php b/export/config/statamic/antlers.php deleted file mode 100644 index 6ec81309..00000000 --- a/export/config/statamic/antlers.php +++ /dev/null @@ -1,60 +0,0 @@ - env('STATAMIC_ANTLERS_DEBUGBAR', true), - - /* - |-------------------------------------------------------------------------- - | Guarded Variables - |-------------------------------------------------------------------------- - | - | Any variable pattern that appears in this list will not be allowed - | in any Antlers template, including any user-supplied values. - | - */ - - 'guardedVariables' => [ - 'config.app.key', - ], - - /* - |-------------------------------------------------------------------------- - | Guarded Tags - |-------------------------------------------------------------------------- - | - | Any tag pattern that appears in this list will not be allowed - | in any Antlers template, including any user-supplied values. - | - */ - - 'guardedTags' => [ - - ], - - /* - |-------------------------------------------------------------------------- - | Guarded Modifiers - |-------------------------------------------------------------------------- - | - | Any modifier pattern that appears in this list will not be allowed - | in any Antlers template, including any user-supplied values. - | - */ - - 'guardedModifiers' => [ - - ], - -]; diff --git a/export/config/statamic/api.php b/export/config/statamic/api.php deleted file mode 100644 index 51168456..00000000 --- a/export/config/statamic/api.php +++ /dev/null @@ -1,99 +0,0 @@ - env('STATAMIC_API_ENABLED', false), - - 'resources' => [ - 'collections' => false, - 'navs' => false, - 'taxonomies' => false, - 'assets' => false, - 'globals' => false, - 'forms' => false, - 'users' => false, - ], - - 'route' => env('STATAMIC_API_ROUTE', 'api'), - - /* - |-------------------------------------------------------------------------- - | Authentication - |-------------------------------------------------------------------------- - | - | By default, the API will be publicly accessible. However, you may define - | an API token here which will be used to authenticate requests. - | - */ - - 'auth_token' => env('STATAMIC_API_AUTH_TOKEN'), - - /* - |-------------------------------------------------------------------------- - | Middleware - |-------------------------------------------------------------------------- - | - | Define the middleware / middleware group that will be applied to the - | API route group. If you want to externally expose this API, here - | you can configure a middleware-based authentication layer. - | - */ - - 'middleware' => env('STATAMIC_API_MIDDLEWARE', 'api'), - - /* - |-------------------------------------------------------------------------- - | Pagination - |-------------------------------------------------------------------------- - | - | The numbers of items to show on each paginated page. - | - */ - - 'pagination_size' => 50, - - /* - |-------------------------------------------------------------------------- - | Caching - |-------------------------------------------------------------------------- - | - | By default, Statamic will cache each endpoint until the specified - | expiry, or until content is changed. See the documentation for - | more details on how to customize your cache implementation. - | - | https://statamic.dev/content-api#caching - | - */ - - 'cache' => [ - 'expiry' => 60, - ], - - /* - |-------------------------------------------------------------------------- - | Exclude Keys - |-------------------------------------------------------------------------- - | - | Here you may provide an array of keys to be excluded from API responses. - | For example, you may want to hide things like edit_url, api_url, etc. - | - */ - - 'excluded_keys' => [ - // - ], - -]; diff --git a/export/config/statamic/assets.php b/export/config/statamic/assets.php deleted file mode 100644 index 2618b48e..00000000 --- a/export/config/statamic/assets.php +++ /dev/null @@ -1,254 +0,0 @@ - [ - - /* - |-------------------------------------------------------------------------- - | Route Prefix - |-------------------------------------------------------------------------- - | - | The route prefix for serving HTTP based manipulated images through Glide. - | If using the cached option, this should be the URL of the cached path. - | - */ - - 'route' => 'img', - - /* - |-------------------------------------------------------------------------- - | Require Glide security token - |-------------------------------------------------------------------------- - | - | With this option enabled, you are protecting your website from mass image - | resize attacks. You will need to generate tokens using the Glide tag - | but may want to disable this while in development to tinker. - | - */ - - 'secure' => true, - - /* - |-------------------------------------------------------------------------- - | Image Manipulation Driver - |-------------------------------------------------------------------------- - | - | The driver that will be used under the hood for image manipulation. - | Supported: "gd", "imagick" or a class name of a custom driver. - | - */ - - 'driver' => 'gd', - - /* - |-------------------------------------------------------------------------- - | Save Cached Images - |-------------------------------------------------------------------------- - | - | Enabling this will make Glide save publicly accessible images. It will - | increase performance at the cost of the dynamic nature of HTTP based - | image manipulation. You will need to invalidate images manually. - | - */ - - 'cache' => false, - 'cache_path' => public_path('img'), - - /* - |-------------------------------------------------------------------------- - | Image Manipulation Defaults - |-------------------------------------------------------------------------- - | - | You may define global defaults for all manipulation parameters, such as - | quality, format, and sharpness. These can and will be overwritten - | on the tag parameter level as well as the preset level. - | - */ - - 'defaults' => [ - // 'quality' => 50, - ], - - /* - |-------------------------------------------------------------------------- - | Image Manipulation Presets - |-------------------------------------------------------------------------- - | - | Rather than specifying your manipulation params in your templates with - | the glide tag, you may define them here and reference their handles. - | They may also be automatically generated when you upload assets. - | Containers can be configured to warm these caches on upload. - | - */ - - 'presets' => [ - // 'small' => ['w' => 200, 'h' => 200, 'q' => 75, 'fit' => 'crop'], - ], - - /* - |-------------------------------------------------------------------------- - | Generate Image Manipulation Presets on Upload - |-------------------------------------------------------------------------- - | - | By default, presets will be automatically generated on upload, ensuring - | the cached images are available when they are first used. You may opt - | out of this behavior here and have the presets generated on demand. - | - */ - - 'generate_presets_on_upload' => true, - - ], - - /* - |-------------------------------------------------------------------------- - | Auto-Crop Assets - |-------------------------------------------------------------------------- - | - | Enabling this will make Glide automatically crop assets at their focal - | point (which is the center if no focal point is defined). Otherwise, - | you will need to manually add any crop related parameters. - | - */ - - 'auto_crop' => true, - - /* - |-------------------------------------------------------------------------- - | Control Panel Thumbnail Restrictions - |-------------------------------------------------------------------------- - | - | Thumbnails will not be generated for any assets any larger (in either - | axis) than the values listed below. This helps prevent memory usage - | issues out of the box. You may increase or decrease as necessary. - | - */ - - 'thumbnails' => [ - 'max_width' => 10000, - 'max_height' => 10000, - ], - - /* - |-------------------------------------------------------------------------- - | Control Panel Video Thumbnails - |-------------------------------------------------------------------------- - | - | When enabled, Statamic will generate thumbnails for videos. - | Generated thumbnails are displayed in the Control Panel. - | - */ - - 'video_thumbnails' => true, - - /* - |-------------------------------------------------------------------------- - | File Previews with Google Docs - |-------------------------------------------------------------------------- - | - | Filetypes that cannot be rendered with HTML5 can opt into the Google Docs - | Viewer. Google will get temporary access to these files so keep that in - | mind for any privacy implications: https://policies.google.com/privacy - | - */ - - 'google_docs_viewer' => false, - - /* - |-------------------------------------------------------------------------- - | Cache Metadata - |-------------------------------------------------------------------------- - | - | Asset metadata (filesize, dimensions, custom data, etc) will get cached - | to optimize performance, so that it will not need to be constantly - | re-evaluated from disk. You may disable this option if you are - | planning to continually modify the same asset repeatedly. - | - */ - - 'cache_meta' => true, - - /* - |-------------------------------------------------------------------------- - | Focal Point Editor - |-------------------------------------------------------------------------- - | - | When editing images in the Control Panel, there is an option to choose - | a focal point. When working with third-party image providers such as - | Cloudinary it can be useful to disable Statamic's built-in editor. - | - */ - - 'focal_point_editor' => true, - - /* - |-------------------------------------------------------------------------- - | Enforce Lowercase Filenames - |-------------------------------------------------------------------------- - | - | Control whether asset filenames will be converted to lowercase when - | uploading and renaming. This can help you avoid file conflicts - | when working in case-insensitive filesystem environments. - | - */ - - 'lowercase' => true, - - /* - |-------------------------------------------------------------------------- - | Additional Uploadable Extensions - |-------------------------------------------------------------------------- - | - | Statamic will only allow uploads of certain approved file extensions. - | If you need to allow more file extensions, you may add them here. - | - */ - - 'additional_uploadable_extensions' => [], - - /* - |-------------------------------------------------------------------------- - | SVG Sanitization - |-------------------------------------------------------------------------- - | - | Statamic will automatically sanitize SVG files when uploaded to avoid - | potential security issues. However, if you have a valid reason for - | disabling this, and you trust your users, you may do so here. - | - */ - - 'svg_sanitization_on_upload' => true, - - /* - |-------------------------------------------------------------------------- - | FFmpeg - |-------------------------------------------------------------------------- - | - | Statamic uses FFmpeg to extract thumbnails from videos to be shown in the - | Control Panel. You may adjust the binary location and cache path here. - | - */ - - 'ffmpeg' => [ - 'binary' => null, - 'cache_path' => storage_path('statamic/glide/ffmpeg'), - ], - - /* - |-------------------------------------------------------------------------- - | Replicator and Bard Set Preview Images - |-------------------------------------------------------------------------- - | - | Replicator and Bard sets may have preview images to give users a visual - | representation of the content within. Here you may specify the asset - | container and folder where these preview images are to be stored. - | - */ - - 'set_preview_images' => [ - 'container' => 'assets', - 'folder' => 'set-previews', - ], - -]; diff --git a/export/config/statamic/autosave.php b/export/config/statamic/autosave.php deleted file mode 100644 index 5f7a0eff..00000000 --- a/export/config/statamic/autosave.php +++ /dev/null @@ -1,36 +0,0 @@ - false, - - /* - |-------------------------------------------------------------------------- - | Default autosave interval - |-------------------------------------------------------------------------- - | - | The default value may be set here and will apply to all collections. - | However, it is also possible to manually adjust the value in the - | each collection's config file. By default, this is set to 5s. - | - */ - - 'interval' => 5000, - -]; diff --git a/export/config/statamic/cp.php b/export/config/statamic/cp.php deleted file mode 100644 index 6c91dca1..00000000 --- a/export/config/statamic/cp.php +++ /dev/null @@ -1,132 +0,0 @@ - env('CP_ENABLED', true), - - 'route' => env('CP_ROUTE', 'cp'), - - /* - |-------------------------------------------------------------------------- - | Authentication - |-------------------------------------------------------------------------- - | - | Whether the Control Panel's authentication pages should be enabled, - | and where users should be redirected in order to authenticate. - | - */ - - 'auth' => [ - 'enabled' => true, - 'redirect_to' => null, - ], - - /* - |-------------------------------------------------------------------------- - | Start Page - |-------------------------------------------------------------------------- - | - | When a user logs into the Control Panel, they will be taken here. - | For example: "dashboard", "collections/pages", etc. - | - */ - - 'start_page' => 'dashboard', - - /* - |-------------------------------------------------------------------------- - | Dashboard Widgets - |-------------------------------------------------------------------------- - | - | Here you may define any number of dashboard widgets. You're free to - | use the same widget multiple times in different configurations. - | - */ - - 'widgets' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Pagination - |-------------------------------------------------------------------------- - | - | Here you may define the default pagination size as well as the options - | the user can select on any paginated listing in the Control Panel. - | - */ - - 'pagination_size' => 50, - - 'pagination_size_options' => [10, 25, 50, 100, 500], - - /* - |-------------------------------------------------------------------------- - | Links to Documentation - |-------------------------------------------------------------------------- - | - | Show contextual links to documentation throughout the Control Panel. - | - */ - - 'link_to_docs' => env('STATAMIC_LINK_TO_DOCS', true), - - /* - |-------------------------------------------------------------------------- - | Support Link - |-------------------------------------------------------------------------- - | - | Set the location of the support link in the "Useful Links" header - | dropdown. Use 'false' to remove it entirely. - | - */ - - 'support_url' => env('STATAMIC_SUPPORT_URL', 'https://statamic.com/support'), - - /* - |-------------------------------------------------------------------------- - | White Labeling - |-------------------------------------------------------------------------- - | - | When in Pro Mode you may replace the Statamic name, logo, favicon, - | and add your own CSS to the control panel to match your - | company or client's brand. - | - */ - - 'custom_cms_name' => env('STATAMIC_CUSTOM_CMS_NAME', 'Statamic'), - - 'custom_logo_url' => env('STATAMIC_CUSTOM_LOGO_URL', null), - - 'custom_dark_logo_url' => env('STATAMIC_CUSTOM_DARK_LOGO_URL', null), - - 'custom_logo_text' => env('STATAMIC_CUSTOM_LOGO_TEXT', null), - - 'custom_favicon_url' => env('STATAMIC_CUSTOM_FAVICON_URL', null), - - 'custom_css_url' => env('STATAMIC_CUSTOM_CSS_URL', null), - - /* - |-------------------------------------------------------------------------- - | Thumbnails - |-------------------------------------------------------------------------- - | - | Here you may define additional CP asset thumbnail presets. - | - */ - - 'thumbnail_presets' => [ - // 'medium' => 800, - ], - -]; diff --git a/export/config/statamic/editions.php b/export/config/statamic/editions.php deleted file mode 100644 index 1dbe5994..00000000 --- a/export/config/statamic/editions.php +++ /dev/null @@ -1,11 +0,0 @@ - env('STATAMIC_PRO_ENABLED', false), - - 'addons' => [ - // - ], - -]; diff --git a/export/config/statamic/forms.php b/export/config/statamic/forms.php deleted file mode 100644 index c2d434f0..00000000 --- a/export/config/statamic/forms.php +++ /dev/null @@ -1,57 +0,0 @@ - resource_path('forms'), - - /* - |-------------------------------------------------------------------------- - | Email View Folder - |-------------------------------------------------------------------------- - | - | The folder under resources/views where your email templates are found. - | - */ - - 'email_view_folder' => null, - - /* - |-------------------------------------------------------------------------- - | Send Email Job - |-------------------------------------------------------------------------- - | - | The class name of the job that will be used to send an email. - | - */ - - 'send_email_job' => \Statamic\Forms\SendEmail::class, - - /* - |-------------------------------------------------------------------------- - | Exporters - |-------------------------------------------------------------------------- - | - | Here you may define all the available form submission exporters. - | You may customize the options within each exporter's array. - | - */ - - 'exporters' => [ - 'csv' => [ - 'class' => Statamic\Forms\Exporters\CsvExporter::class, - ], - 'json' => [ - 'class' => Statamic\Forms\Exporters\JsonExporter::class, - ], - ], - -]; diff --git a/export/config/statamic/git.php b/export/config/statamic/git.php deleted file mode 100644 index 7c569b04..00000000 --- a/export/config/statamic/git.php +++ /dev/null @@ -1,185 +0,0 @@ - env('STATAMIC_GIT_ENABLED', false), - - /* - |-------------------------------------------------------------------------- - | Automatically Run - |-------------------------------------------------------------------------- - | - | By default, commits are automatically queued when `Saved` or `Deleted` - | events are fired. If you prefer users to manually trigger commits - | using the `Git` utility interface, you may set this to `false`. - | - | https://statamic.dev/git-automation#committing-changes - | - */ - - 'automatic' => env('STATAMIC_GIT_AUTOMATIC', true), - - /* - |-------------------------------------------------------------------------- - | Queue Connection - |-------------------------------------------------------------------------- - | - | You may choose which queue connection should be used when dispatching - | commit jobs. Unless specified, the default connection will be used. - | - | https://statamic.dev/git-automation#queueing-commits - | - */ - - 'queue_connection' => env('STATAMIC_GIT_QUEUE_CONNECTION'), - - /* - |-------------------------------------------------------------------------- - | Dispatch Delay - |-------------------------------------------------------------------------- - | - | When `Saved` and `Deleted` events queue up commits, you may wish to - | set a delay time in minutes for each queued job. This can allow - | for more consolidated commits when you have multiple users - | making simultaneous content changes to your repository. - | - | Note: Not supported by default `sync` queue driver. - | - */ - - 'dispatch_delay' => env('STATAMIC_GIT_DISPATCH_DELAY', 0), - - /* - |-------------------------------------------------------------------------- - | Git User - |-------------------------------------------------------------------------- - | - | The git user that will be used when committing changes. By default, it - | will attempt to commit with the authenticated user's name and email - | when possible, falling back to the below user when not available. - | - | https://statamic.dev/git-automation#git-user - | - */ - - 'use_authenticated' => true, - - 'user' => [ - 'name' => env('STATAMIC_GIT_USER_NAME', 'Spock'), - 'email' => env('STATAMIC_GIT_USER_EMAIL', 'spock@example.com'), - ], - - /* - |-------------------------------------------------------------------------- - | Tracked Paths - |-------------------------------------------------------------------------- - | - | Define the tracked paths to be considered when staging changes. Default - | stache and file locations are already set up for you, but feel free - | to modify these paths to suit your storage config. Referencing - | absolute paths to external repos is also completely valid. - | - */ - - 'paths' => [ - base_path('content'), - base_path('users'), - resource_path('addons'), - resource_path('blueprints'), - resource_path('fieldsets'), - resource_path('forms'), - resource_path('users'), - resource_path('preferences.yaml'), - resource_path('sites.yaml'), - storage_path('forms'), - public_path('assets'), - ], - - /* - |-------------------------------------------------------------------------- - | Git Binary - |-------------------------------------------------------------------------- - | - | By default, Statamic will try to use the "git" command, but you can set - | an absolute path to the git binary if necessary for your environment. - | - */ - - 'binary' => env('STATAMIC_GIT_BINARY', 'git'), - - /* - |-------------------------------------------------------------------------- - | Commands - |-------------------------------------------------------------------------- - | - | Define a list commands to be run when Statamic is ready to `git add` - | and `git commit` your changes. These commands will be run once - | per repo, attempting to consolidate commits where possible. - | - | https://statamic.dev/git-automation#customizing-commits - | - */ - - 'commands' => [ - '{{ git }} add {{ paths }}', - '{{ git }} -c "user.name={{ name }}" -c "user.email={{ email }}" commit -m "{{ message }}"', - ], - - /* - |-------------------------------------------------------------------------- - | Push - |-------------------------------------------------------------------------- - | - | Determine whether `git push` should be run after the commands above - | have finished. This is disabled by default, but can be enabled - | globally, or per environment using the provided variable. - | - | https://statamic.dev/git-automation#pushing-changes - | - */ - - 'push' => env('STATAMIC_GIT_PUSH', false), - - /* - |-------------------------------------------------------------------------- - | Ignored Events - |-------------------------------------------------------------------------- - | - | Statamic will listen on all `Saved` and `Deleted` events, as well - | as any events registered by installed addons. If you wish to - | ignore any specific events, you may reference them here. - | - */ - - 'ignored_events' => [ - // \Statamic\Events\UserSaved::class, - // \Statamic\Events\UserDeleted::class, - ], - - /* - |-------------------------------------------------------------------------- - | Locale - |-------------------------------------------------------------------------- - | - | The locale to be used when translating commit messages, etc. By - | default, the authenticated user's locale will be used, but - | feel free to override this using the provided variable. - | - */ - - 'locale' => env('STATAMIC_GIT_LOCALE', null), - -]; diff --git a/export/config/statamic/graphql.php b/export/config/statamic/graphql.php deleted file mode 100644 index 02f8258c..00000000 --- a/export/config/statamic/graphql.php +++ /dev/null @@ -1,91 +0,0 @@ - env('STATAMIC_GRAPHQL_ENABLED', false), - - 'resources' => [ - 'collections' => false, - 'navs' => false, - 'taxonomies' => false, - 'assets' => false, - 'globals' => false, - 'forms' => false, - 'sites' => false, - 'users' => false, - ], - - /* - |-------------------------------------------------------------------------- - | Queries - |-------------------------------------------------------------------------- - | - | Here you may list queries to be added to the Statamic schema. - | - | https://statamic.dev/graphql#custom-queries - | - */ - - 'queries' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Mutations - |-------------------------------------------------------------------------- - | - | Here you may list mutations to be added to the Statamic schema. - | - | https://statamic.dev/graphql#custom-mutations - */ - - 'mutations' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Middleware - |-------------------------------------------------------------------------- - | - | Here you may list middleware to be added to the Statamic schema. - | - | https://statamic.dev/graphql#custom-middleware - | - */ - - 'middleware' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Caching - |-------------------------------------------------------------------------- - | - | By default, Statamic will cache each request until the specified - | expiry, or until content is changed. See the documentation for - | more details on how to customize your cache implementation. - | - | https://statamic.dev/graphql#caching - | - */ - - 'cache' => [ - 'expiry' => 60, - ], - -]; diff --git a/export/config/statamic/live_preview.php b/export/config/statamic/live_preview.php deleted file mode 100644 index b5da9a0f..00000000 --- a/export/config/statamic/live_preview.php +++ /dev/null @@ -1,60 +0,0 @@ - [ - 'Laptop' => ['width' => 1440, 'height' => 900], - 'Tablet' => ['width' => 1024, 'height' => 786], - 'Mobile' => ['width' => 375, 'height' => 812], - ], - - /* - |-------------------------------------------------------------------------- - | Additional Inputs - |-------------------------------------------------------------------------- - | - | Additional fields may be added to the Live Preview header bar. You - | may define a list of Vue components to be injected. Their values - | will be added to the cascade on the front-end for you to use. - | - */ - - 'inputs' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Force Reload Javascript Modules - |-------------------------------------------------------------------------- - | - | To force a reload, Live Preview appends a timestamp to the URL on - | script tags of type 'module'. You may disable this behavior here. - | - */ - - 'force_reload_js_modules' => true, - - /* - |-------------------------------------------------------------------------- - | Hot Reload Contents - |-------------------------------------------------------------------------- - | - | Should the Live Preview embed be hot-reloaded when the content changes? - | Only applies when "Refresh" is disabled on the live preview target. - | - */ - - 'hot_reload_contents' => true, - -]; diff --git a/export/config/statamic/oauth.php b/export/config/statamic/oauth.php deleted file mode 100644 index d7e3fd24..00000000 --- a/export/config/statamic/oauth.php +++ /dev/null @@ -1,69 +0,0 @@ - env('STATAMIC_OAUTH_ENABLED', false), - - 'email_login_enabled' => true, - - 'providers' => [ - // 'github', - ], - - 'routes' => [ - 'login' => 'oauth/{provider}', - 'callback' => 'oauth/{provider}/callback', - ], - - /* - |-------------------------------------------------------------------------- - | Create User - |-------------------------------------------------------------------------- - | - | Whether or not a user account should be created upon authentication - | with an OAuth provider. If disabled, a user account will be need - | to be explicitly created ahead of time. - | - */ - - 'create_user' => true, - - /* - |-------------------------------------------------------------------------- - | Merge User Data - |-------------------------------------------------------------------------- - | - | When authenticating with an OAuth provider, the user data returned - | such as their name will be merged with the existing user account. - | - */ - - 'merge_user_data' => true, - - /* - |-------------------------------------------------------------------------- - | Unauthorized Redirect - |-------------------------------------------------------------------------- - | - | This controls where the user is taken after authenticating with - | an OAuth provider but their account is unauthorized. This may - | happen when the create_user option has been set to false. - | - */ - - 'unauthorized_redirect' => null, - - /* - |-------------------------------------------------------------------------- - | Remember Me - |-------------------------------------------------------------------------- - | - | Whether or not the "remember me" functionality should be used when - | authenticating using OAuth. When enabled, the user will remain - | logged in indefinitely, or until they manually log out. - | - */ - - 'remember_me' => true, - -]; diff --git a/export/config/statamic/protect.php b/export/config/statamic/protect.php deleted file mode 100644 index 4e78f78a..00000000 --- a/export/config/statamic/protect.php +++ /dev/null @@ -1,53 +0,0 @@ - null, - - /* - |-------------------------------------------------------------------------- - | Protection Schemes - |-------------------------------------------------------------------------- - | - | Here you may define all of the protection schemes for your application - | as well as their drivers. You may even define multiple schemes for - | the same driver to easily protect different types of pages. - | - | Supported drivers: "ip_address", "auth", "password" - | - */ - - 'schemes' => [ - - 'ip_address' => [ - 'driver' => 'ip_address', - 'allowed' => ['127.0.0.1'], - ], - - 'logged_in' => [ - 'driver' => 'auth', - 'login_url' => '/login', - 'append_redirect' => true, - ], - - 'password' => [ - 'driver' => 'password', - 'allowed' => ['secret'], - 'field' => null, - 'form_url' => null, - ], - - ], - -]; diff --git a/export/config/statamic/revisions.php b/export/config/statamic/revisions.php deleted file mode 100644 index c81fc8f7..00000000 --- a/export/config/statamic/revisions.php +++ /dev/null @@ -1,18 +0,0 @@ - env('STATAMIC_REVISIONS_ENABLED', false), - -]; diff --git a/export/config/statamic/routes.php b/export/config/statamic/routes.php deleted file mode 100644 index 95a64276..00000000 --- a/export/config/statamic/routes.php +++ /dev/null @@ -1,56 +0,0 @@ - true, - - /* - |-------------------------------------------------------------------------- - | Enable Route Bindings - |-------------------------------------------------------------------------- - | - | Whether route bindings for Statamic repositories (entry, taxonomy, - | collections, etc) are enabled for front end routes. This may be - | useful if you want to make your own custom routes with them. - | - */ - - 'bindings' => false, - - /* - |-------------------------------------------------------------------------- - | Action Route Prefix - |-------------------------------------------------------------------------- - | - | Some extensions may provide routes that go through the frontend of your - | website. These URLs begin with the following prefix. We've chosen an - | unobtrusive default but you are free to select whatever you want. - | - */ - - 'action' => '!', - - /* - |-------------------------------------------------------------------------- - | Middleware - |-------------------------------------------------------------------------- - | - | Define the middleware that will be applied to the web route group. - | - */ - - 'middleware' => 'web', - -]; diff --git a/export/config/statamic/search.php b/export/config/statamic/search.php deleted file mode 100644 index 49b0ffde..00000000 --- a/export/config/statamic/search.php +++ /dev/null @@ -1,109 +0,0 @@ - env('STATAMIC_DEFAULT_SEARCH_INDEX', 'default'), - - /* - |-------------------------------------------------------------------------- - | Search Indexes - |-------------------------------------------------------------------------- - | - | Here you can define all of the available search indexes. - | - */ - - 'indexes' => [ - - 'default' => [ - 'driver' => 'local', - 'searchables' => 'content', - 'fields' => ['title'], - ], - - // 'blog' => [ - // 'driver' => 'local', - // 'searchables' => 'collection:blog', - // ], - - ], - - /* - |-------------------------------------------------------------------------- - | Driver Defaults - |-------------------------------------------------------------------------- - | - | Here you can specify default configuration to be applied to all indexes - | that use the corresponding driver. For instance, if you have two - | indexes that use the "local" driver, both of them can have the - | same base configuration. You may override for each index. - | - */ - - 'drivers' => [ - - 'local' => [ - 'path' => storage_path('statamic/search'), - ], - - 'algolia' => [ - 'credentials' => [ - 'id' => env('ALGOLIA_APP_ID', ''), - 'secret' => env('ALGOLIA_SECRET', ''), - ], - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Search Defaults - |-------------------------------------------------------------------------- - | - | Here you can specify default configuration to be applied to all indexes - | regardless of the driver. You can override these per driver or per index. - | - */ - - 'defaults' => [ - 'fields' => ['title'], - ], - - /* - |-------------------------------------------------------------------------- - | Indexing Queue - |-------------------------------------------------------------------------- - | - | Here you may configure the queue name and connection used when indexing - | documents. - | - */ - - 'queue' => env('STATAMIC_SEARCH_QUEUE'), - - 'queue_connection' => env('STATAMIC_SEARCH_QUEUE_CONNECTION'), - - /* - |-------------------------------------------------------------------------- - | Chunk Size - |-------------------------------------------------------------------------- - | - | Here you can configure the chunk size used when indexing documents. - | The higher you make it, the more memory it will use, but the quicker - | the indexing process will be. - | - */ - - 'chunk_size' => 100, - -]; diff --git a/export/config/statamic/stache.php b/export/config/statamic/stache.php deleted file mode 100644 index 9677602e..00000000 --- a/export/config/statamic/stache.php +++ /dev/null @@ -1,100 +0,0 @@ - env('STATAMIC_STACHE_WATCHER', 'auto'), - - /* - |-------------------------------------------------------------------------- - | Cache Store - |-------------------------------------------------------------------------- - | - | Here you may configure which Cache Store the Stache uses. - | - */ - - 'cache_store' => null, - - /* - |-------------------------------------------------------------------------- - | Stores - |-------------------------------------------------------------------------- - | - | Here you may configure the stores that are used inside the Stache. - | - | https://statamic.dev/stache#stores - | - */ - - 'stores' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Indexes - |-------------------------------------------------------------------------- - | - | Here you may define any additional indexes that will be inherited - | by each store in the Stache. You may also define indexes on a - | per-store level by adding an "indexes" key to its config. - | - */ - - 'indexes' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Locking - |-------------------------------------------------------------------------- - | - | In order to prevent concurrent requests from updating the Stache at the - | same time and wasting resources, it will be locked so that subsequent - | requests will have to wait until the first one has been completed. - | - | https://statamic.dev/stache#locks - | - */ - - 'lock' => [ - 'enabled' => true, - 'timeout' => 30, - ], - - /* - |-------------------------------------------------------------------------- - | Warming Optimization - |-------------------------------------------------------------------------- - | - | These options control performance optimizations during Stache warming. - | - */ - - 'warming' => [ - // Enable parallel store processing for faster warming on multi-core systems - 'parallel_processing' => env('STATAMIC_STACHE_PARALLEL_WARMING', false), - - // Maximum number of parallel processes (0 = auto-detect CPU cores) - 'max_processes' => env('STATAMIC_STACHE_MAX_PROCESSES', 0), - - // Minimum number of stores required to enable parallel processing - 'min_stores_for_parallel' => env('STATAMIC_STACHE_MIN_STORES_PARALLEL', 3), - - // Concurrency driver: 'process', 'fork', or 'sync' - 'concurrency_driver' => env('STATAMIC_STACHE_CONCURRENCY_DRIVER', 'process'), - ], - -]; diff --git a/export/config/statamic/static_caching.php b/export/config/statamic/static_caching.php deleted file mode 100644 index 738863c9..00000000 --- a/export/config/statamic/static_caching.php +++ /dev/null @@ -1,193 +0,0 @@ - env('STATAMIC_STATIC_CACHING_STRATEGY', null), - - /* - |-------------------------------------------------------------------------- - | Caching Strategies - |-------------------------------------------------------------------------- - | - | Here you may define all of the static caching strategies for your - | application as well as their drivers. - | - | Supported drivers: "application", "file" - | - */ - - 'strategies' => [ - - 'half' => [ - 'driver' => 'application', - 'expiry' => null, - ], - - 'full' => [ - 'driver' => 'file', - 'path' => public_path('static'), - 'lock_hold_length' => 0, - 'permissions' => [ - 'directory' => 0755, - 'file' => 0644, - ], - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Exclusions - |-------------------------------------------------------------------------- - | - | Here you may define a list of URLs to be excluded from static - | caching. You may want to exclude URLs containing dynamic - | elements like contact forms, or shopping carts. - | - */ - - 'exclude' => [ - - 'class' => null, - - 'urls' => [ - // - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Invalidation Rules - |-------------------------------------------------------------------------- - | - | Here you may define the rules that trigger when and how content would be - | flushed from the static cache. See the documentation for more details. - | If a custom class is not defined, the default invalidator is used. - | - | https://statamic.dev/static-caching - | - */ - - 'invalidation' => [ - - 'class' => null, - - 'rules' => [ - // - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Ignoring Query Strings - |-------------------------------------------------------------------------- - | - | Statamic will cache pages of the same URL but with different query - | parameters separately. This is useful for pages with pagination. - | If you'd like to ignore the query strings, you may do so. - | - */ - - 'ignore_query_strings' => false, - - 'allowed_query_strings' => [ - // - ], - - 'disallowed_query_strings' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Nocache - |-------------------------------------------------------------------------- - | - | Here you may define where the nocache data is stored. - | - | https://statamic.dev/tags/nocache#database - | - | Supported drivers: "cache", "database" - | - */ - - 'nocache' => 'cache', - - 'nocache_db_connection' => env('STATAMIC_NOCACHE_DB_CONNECTION'), - - /* - |-------------------------------------------------------------------------- - | Replacers - |-------------------------------------------------------------------------- - | - | Here you may define replacers that dynamically replace content within - | the response. Each replacer must implement the Replacer interface. - | - */ - - 'replacers' => [ - \Statamic\StaticCaching\Replacers\CsrfTokenReplacer::class, - \Statamic\StaticCaching\Replacers\NoCacheReplacer::class, - ], - - /* - |-------------------------------------------------------------------------- - | Warm Queue - |-------------------------------------------------------------------------- - | - | Here you may define the queue name and connection - | that will be used when warming the static cache and - | optionally set the "--insecure" flag by default. - | - */ - - 'warm_queue' => env('STATAMIC_STATIC_WARM_QUEUE'), - - 'warm_queue_connection' => env('STATAMIC_STATIC_WARM_QUEUE_CONNECTION'), - - 'warm_insecure' => env('STATAMIC_STATIC_WARM_INSECURE', false), - - /* - |-------------------------------------------------------------------------- - | Background Re-cache - |-------------------------------------------------------------------------- - | - | When this enabled, Statamic will re-cache URLs in the background, - | overwriting the existing cache, without removing it first. - | - */ - - 'background_recache' => env('STATAMIC_BACKGROUND_RECACHE', false), - - 'recache_token' => env('STATAMIC_RECACHE_TOKEN'), - - 'recache_token_parameter' => '__recache', - - /* - |-------------------------------------------------------------------------- - | Shared Error Pages - |-------------------------------------------------------------------------- - | - | You may choose to share the same statically generated error page across - | all errors. For example, the first time a 404 is encountered it will - | be generated and cached, and then served for all subsequent 404s. - | - | This is only supported for half measure. - | - */ - - 'share_errors' => false, - -]; diff --git a/export/config/statamic/system.php b/export/config/statamic/system.php deleted file mode 100644 index 3ed5d9a7..00000000 --- a/export/config/statamic/system.php +++ /dev/null @@ -1,272 +0,0 @@ - env('STATAMIC_LICENSE_KEY'), - - /* - |-------------------------------------------------------------------------- - | Enable Multi-site - |-------------------------------------------------------------------------- - | - | Whether Statamic's multi-site functionality should be enabled. It is - | assumed Statamic Pro is also enabled. To get started, you can run - | the `php please multisite` command to update your content file - | structure, after which you can manage your sites in the CP. - | - | https://statamic.dev/multi-site - | - */ - - 'multisite' => false, - - /* - |-------------------------------------------------------------------------- - | Default Addons Paths - |-------------------------------------------------------------------------- - | - | When generating addons via `php please make:addon`, this path will be - | used by default. You can still specify custom repository paths in - | your composer.json, but this is the path used by the generator. - | - */ - - 'addons_path' => base_path('addons'), - - /* - |-------------------------------------------------------------------------- - | Blueprints Path - |-------------------------------------------------------------------------- - | - | Where your blueprint YAML files are stored. - | - */ - - 'blueprints_path' => resource_path('blueprints'), - - /* - |-------------------------------------------------------------------------- - | Fieldsets Path - |-------------------------------------------------------------------------- - | - | Where your fieldset YAML files are stored. - | - */ - - 'fieldsets_path' => resource_path('fieldsets'), - - /* - |-------------------------------------------------------------------------- - | Send the Powered-By Header - |-------------------------------------------------------------------------- - | - | Websites like builtwith.com use the X-Powered-By header to determine - | what technologies are used on a particular site. By default, we'll - | send this header, but you are absolutely allowed to disable it. - | - */ - - 'send_powered_by_header' => true, - - /* - |-------------------------------------------------------------------------- - | Date Format - |-------------------------------------------------------------------------- - | - | Whenever a Carbon date is cast to a string on front-end routes, it will - | use this format. On CP routes, the format defined in cp.php is used. - | You can customize this format using PHP's date string constants. - | Setting this value to null will use Carbon's default format. - | - | https://www.php.net/manual/en/function.date.php - | - */ - - 'date_format' => 'F jS, Y', - - /* - |-------------------------------------------------------------------------- - | Timezone - |-------------------------------------------------------------------------- - | - | Statamic will use this timezone when displaying dates on the front-end. - | You can use any timezone supported by PHP. When set to null it will - | fall back to the timezone defined in your `app.php` config file. - | - | https://www.php.net/manual/en/timezones.php - | - */ - - 'display_timezone' => null, - - /* - |-------------------------------------------------------------------------- - | Localize Dates in Modifiers - |-------------------------------------------------------------------------- - | - | When using date-related modifiers, Carbon instances will be in UTC. - | Enabling this setting will ensure that dates get localized into - | the timezone defined in `display_timezone`. Otherwise you'll - | need to manually localize dates in all of your templates. - | - */ - - 'localize_dates_in_modifiers' => false, - - /* - |-------------------------------------------------------------------------- - | Default Character Set - |-------------------------------------------------------------------------- - | - | Statamic will use this character set when performing specific string - | encoding and decoding operations; This does not apply everywhere. - | - */ - - 'charset' => 'UTF-8', - - /* - |-------------------------------------------------------------------------- - | Track Last Update - |-------------------------------------------------------------------------- - | - | Statamic will automatically set an `updated_at` timestamp (along with - | `updated_by`, where applicable) when specific content is updated. - | In some situations, you may wish disable this functionality. - | - */ - - 'track_last_update' => true, - - /* - |-------------------------------------------------------------------------- - | Enable Cache Tags - |-------------------------------------------------------------------------- - | - | Sometimes you'll want to be able to disable the {{ cache }} tags in - | Antlers, so here is where you can do that. Otherwise, it will be - | enabled all the time. - | - */ - - 'cache_tags_enabled' => env('STATAMIC_CACHE_TAGS_ENABLED', true), - - /* - |-------------------------------------------------------------------------- - | Intensive Operations - |-------------------------------------------------------------------------- - | - | Sometimes Statamic requires extra resources to complete intensive - | operations. Here you may configure system resource limits for - | those rare times when we need to turn things up to eleven! - | - */ - - 'php_memory_limit' => '-1', - 'php_max_execution_time' => '0', - 'ajax_timeout' => '600000', - 'pcre_backtrack_limit' => '-1', - - /* - |-------------------------------------------------------------------------- - | Debugbar Integration - |-------------------------------------------------------------------------- - | - | Statamic integrates with Laravel Debugbar to bring more detail to your - | debugging experience. Here you may adjust various default options. - | - */ - - 'debugbar' => [ - 'pretty_print_variables' => true, - ], - - /* - |-------------------------------------------------------------------------- - | ASCII - |-------------------------------------------------------------------------- - | - | During various string manipulations (e.g. slugification), Statamic will - | need to make ASCII character conversions. Here you may define whether - | or not extra characters get converted. e.g. "%" becomes "percent". - | - */ - - 'ascii_replace_extra_symbols' => false, - - /* - |-------------------------------------------------------------------------- - | Update References on Change - |-------------------------------------------------------------------------- - | - | With this enabled, Statamic will attempt to update references to assets - | and terms when moving, renaming, replacing, deleting, etc. This will - | be queued, but it can disabled as needed for performance reasons. - | - */ - - 'update_references' => true, - - /* - |-------------------------------------------------------------------------- - | Always Augment to Query - |-------------------------------------------------------------------------- - | - | By default, Statamic will augment relationship fields with max_items: 1 - | to the result of a query, for example an Entry instance. Setting this - | to true will augment to the query builder instead of the result. - | - */ - - 'always_augment_to_query' => false, - - /* - |-------------------------------------------------------------------------- - | Row ID handle - |-------------------------------------------------------------------------- - | - | Rows in Grid, Replicator, and Bard fields will be given a unique ID using - | the "id" field. You may need your own field named "id", in which case - | you may customize the handle of the field that Statamic will use. - | - */ - - 'row_id_handle' => 'id', - - /* - |-------------------------------------------------------------------------- - | Fake SQL Queries - |-------------------------------------------------------------------------- - | - | Enable while using the flat-file Stache driver to show fake "SQL" query - | approximations in your database debugging tools — including Debugbar, - | Laravel Telescope, and Ray with the ray()->showQueries() helper. - | - */ - - 'fake_sql_queries' => config('app.debug'), - - /* - |-------------------------------------------------------------------------- - | Layout - |-------------------------------------------------------------------------- - | - | Define the default layout that will be used by views. - | - */ - - 'layout' => env('STATAMIC_LAYOUT', 'layout'), - -]; diff --git a/export/config/statamic/templates.php b/export/config/statamic/templates.php deleted file mode 100644 index a6102081..00000000 --- a/export/config/statamic/templates.php +++ /dev/null @@ -1,45 +0,0 @@ - 'antlers', - - /* - |-------------------------------------------------------------------------- - | Code Style - |-------------------------------------------------------------------------- - | - | Here you may configure the code generator's output style. - | - */ - - 'style' => [ - 'line_ending' => 'auto', - 'indent_type' => 'space', - 'indent_size' => 4, - 'final_newline' => false, - ], - - /* - |-------------------------------------------------------------------------- - | Antlers Settings - |-------------------------------------------------------------------------- - | - | Antlers specific template generation settings. - | - */ - - 'antlers' => [ - 'use_components' => false, - ], -]; diff --git a/export/config/statamic/users.php b/export/config/statamic/users.php deleted file mode 100644 index a06e5986..00000000 --- a/export/config/statamic/users.php +++ /dev/null @@ -1,209 +0,0 @@ - 'file', - - 'repositories' => [ - - 'file' => [ - 'driver' => 'file', - 'paths' => [ - 'roles' => resource_path('users/roles.yaml'), - 'groups' => resource_path('users/groups.yaml'), - ], - ], - - 'eloquent' => [ - 'driver' => 'eloquent', - ], - - ], - - /* - |-------------------------------------------------------------------------- - | Avatars - |-------------------------------------------------------------------------- - | - | User avatars are initials by default, with custom options for services - | like Gravatar.com. - | - | Supported: "initials", "gravatar", or a custom class name. - | - */ - - 'avatars' => 'initials', - - /* - |-------------------------------------------------------------------------- - | New User Roles - |-------------------------------------------------------------------------- - | - | When registering new users through the user:register_form tag, these - | roles will automatically be applied to your newly created users. - | - */ - - 'new_user_roles' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | New User Groups - |-------------------------------------------------------------------------- - | - | When registering new users through the user:register_form tag, these - | groups will automatically be applied to your newly created users. - | - */ - - 'new_user_groups' => [ - // - ], - - /* - |-------------------------------------------------------------------------- - | Registration form honeypot field - |-------------------------------------------------------------------------- - | - | When registering new users through the user:register_form tag, - | specify the field to act as a honeypot for bots - | - */ - - 'registration_form_honeypot_field' => null, - - /* - |-------------------------------------------------------------------------- - | User Wizard Invitation Email - |-------------------------------------------------------------------------- - | - | When creating new users through the wizard in the control panel, - | you may choose whether to be able to send an invitation email. - | Setting to true will give the user the option. But setting - | it to false will disable the invitation option entirely. - | - */ - - 'wizard_invitation' => true, - - /* - |-------------------------------------------------------------------------- - | Password Brokers - |-------------------------------------------------------------------------- - | - | When resetting passwords, Statamic uses an appropriate password broker. - | Here you may define which broker should be used for each situation. - | You may want a longer expiry for user activations, for example. - | - */ - - 'passwords' => [ - 'resets' => 'users', - 'activations' => 'activations', - ], - - /* - |-------------------------------------------------------------------------- - | Database - |-------------------------------------------------------------------------- - | - | Here you may configure the database connection and its table names. - | - */ - - 'database' => config('database.default'), - - 'tables' => [ - 'users' => 'users', - 'role_user' => 'role_user', - 'roles' => false, - 'group_user' => 'group_user', - 'groups' => false, - 'webauthn' => 'webauthn', - ], - - /* - |-------------------------------------------------------------------------- - | Authentication Guards - |-------------------------------------------------------------------------- - | - | By default, Statamic will use the `web` authentication guard. However, - | if you want to run Statamic alongside the default Laravel auth - | guard, you can configure that for your cp and/or frontend. - | - */ - - 'guards' => [ - 'cp' => 'web', - 'web' => 'web', - ], - - /* - |-------------------------------------------------------------------------- - | Impersonation - |-------------------------------------------------------------------------- - | - | Here you can configure if impersonation is available, and what URL to - | redirect to after impersonation begins. - | - */ - - 'impersonate' => [ - 'enabled' => env('STATAMIC_IMPERSONATE_ENABLED', true), - 'redirect' => env('STATAMIC_IMPERSONATE_REDIRECT', null), - ], - - /* - |-------------------------------------------------------------------------- - | Elevated Sessions - |-------------------------------------------------------------------------- - | - | Users may be required to reauthorize before performing certain - | sensitive actions. This is called an elevated session. Here - | you may configure the duration of the session in minutes. - | - */ - - 'elevated_session_duration' => 15, - - /* - |-------------------------------------------------------------------------- - | Enforce Two-Factor Authentication - |-------------------------------------------------------------------------- - | - | Specify which user roles should be required to enable two-factor - | authentication. Use "*" to enforce 2FA for all users, or "super_users" - | to enforce it for super users. - | - */ - - 'two_factor_enforced_roles' => [], - - /* - |-------------------------------------------------------------------------- - | Default Sorting - |-------------------------------------------------------------------------- - | - | Here you may configure the default sort behavior for user listings. - | - */ - - 'sort_field' => 'email', - 'sort_direction' => 'asc', - -]; diff --git a/export/config/statamic/webauthn.php b/export/config/statamic/webauthn.php deleted file mode 100644 index 378f19d8..00000000 --- a/export/config/statamic/webauthn.php +++ /dev/null @@ -1,41 +0,0 @@ - true, - - /* - |-------------------------------------------------------------------------- - | Remember Me - |-------------------------------------------------------------------------- - | - | Whether or not the "remember me" functionality should be used when - | authenticating using WebAuthn. When enabled, the user will remain - | logged in indefinitely, or until they manually log out. - | - */ - - 'remember_me' => true, - - /* - |-------------------------------------------------------------------------- - | Model - |-------------------------------------------------------------------------- - | - | When using eloquent passkeys you can specify the model you want to use - | - */ - - 'model' => \Statamic\Auth\Eloquent\WebAuthnModel::class, - -]; diff --git a/starter-kit.yaml b/starter-kit.yaml index 533a86bb..03b1cf7d 100644 --- a/starter-kit.yaml +++ b/starter-kit.yaml @@ -6,7 +6,8 @@ export_paths: - app/Providers - app/Services - app/Tags - - config + - config/dok.export.php + - config/statamic/markdown.php - public/assets - content/assets - public/apple-touch-icon.png