mirror of
https://github.com/bitinflow/expose.git
synced 2026-03-13 13:35:54 +00:00
86 lines
3.2 KiB
PHP
86 lines
3.2 KiB
PHP
<?php
|
|
|
|
return [
|
|
'host' => 'localhost',
|
|
'port' => 8080,
|
|
'auth_token' => '',
|
|
|
|
'admin' => [
|
|
|
|
'database' => base_path('database/expose.db'),
|
|
|
|
'validate_auth_tokens' => false,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Maximum connection length
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| If you want to limit the amount of time that a single connection can
|
|
| stay connected to the expose server, you can specify the maximum
|
|
| connection length in minutes here. A maximum length of 0 means that
|
|
| clients can stay connected as long as they want.
|
|
|
|
|
*/
|
|
'maximum_connection_length' => 0,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Subdomain
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the subdomain that your expose admin dashboard will be available at.
|
|
| The given subdomain will be reserved, so no other tunnel connection can
|
|
| request this subdomain for their own connection.
|
|
|
|
|
*/
|
|
'subdomain' => 'expose',
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Subdomain Generator
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the subdomain generator that will be used, when no specific
|
|
| subdomain was provided. The default implementation simply generates
|
|
| a random string for you. Feel free to change this.
|
|
|
|
|
*/
|
|
'subdomain_generator' => \App\Server\SubdomainGenerator\RandomSubdomainGenerator::class,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Users
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| The admin dashboard of expose is protected via HTTP basic authentication
|
|
| Here you may add the user/password combinations that you want to
|
|
| accept as valid logins for the dashboard.
|
|
|
|
|
*/
|
|
'users' => [
|
|
'username' => 'password'
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| User Repository
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the user repository, which by default loads and saves all authorized
|
|
| users in a SQLite database. You can implement your own user repository
|
|
| if you want to store your users in a different store (Redis, MySQL, etc.)
|
|
|
|
|
*/
|
|
'user_repository' => \App\Server\UserRepository\DatabaseUserRepository::class,
|
|
|
|
'messages' => [
|
|
'message_of_the_day' => 'Thank you for using expose.',
|
|
|
|
'invalid_auth_token' => 'Authentication failed. Please check your authentication token and try again.',
|
|
|
|
'subdomain_taken' => 'The chosen subdomain :subdomain is already taken. Please choose a different subdomain.',
|
|
]
|
|
]
|
|
];
|