059f069ef4
Replaces the per-scene HTML directories (landing/, loading/, game/,
desktop/, goodbye/, music-box/, music/) with a single Laravel app
serving every overlay over HTTP. Supervisord runs `php artisan serve`
on 127.0.0.1:1118 and the OBS scene JSON now references HTTP routes
instead of file:// URLs.
Highlights:
- public/css/hud.css consolidates the duplicated HUD chrome,
scanlines/vignette/flicker, terminal styling, and pulse keyframes
that were copy-pasted across all seven scenes.
- Blade partials own hud-strip, crt-overlays, obs-ws-scripts,
camera-frame, screen-frame; the seven scenes extend a shared
overlay layout.
- Artisan commands (`rig:setup`, `rig:telemetry`, `rig:loading`,
`rig:playlist`, `rig:cmd`) replace the shell scripts that wrote
per-rig JSON snapshots. TwitchHelix + HardwareSnapshot services
handle the work the bash + Python helpers used to.
- ObsWsClient + MusicCommandController kill the 250 ms cmd.js poll
in the music daemon: POST /cmd/{skip|prev|pause|resume} opens a
short-lived Pawl WS, authenticates, and broadcasts mpd:cmd.
- AudioController streams files from the configured music dirs so
CEF can load tracks under the HTTP origin (Chromium blocks
HTTP-origin pages from loading file:// media).
- DataController serves /data/playlist.js (with ETag mtime cache)
and /cover.jpg (no-store) so the existing overlays' window.__PLAYLIST
and cover.jpg cache-bust pattern keeps working.
scripts/obs-webapp.supervisord.conf is the supervisord unit; install
to /etc/supervisor.d/obs-webapp.conf.
scripts/rewrite-scene-urls.py is a one-shot tool that rewrites
basic/scenes/Default_Stream_HUD.json from file:// to HTTP URLs.
basic/scenes/Default_Stream_HUD.json.pre-webapp is the rollback
artifact (made with OBS closed; full pre-migration state).
The seven old scene directories, vendor/, and the bash scripts are
still on disk pending visual verification; the next commit will
prune them.
118 lines
3.9 KiB
PHP
118 lines
3.9 KiB
PHP
<?php
|
|
|
|
use App\Models\User;
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Authentication Defaults
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This option defines the default authentication "guard" and password
|
|
| reset "broker" for your application. You may change these values
|
|
| as required, but they're a perfect start for most applications.
|
|
|
|
|
*/
|
|
|
|
'defaults' => [
|
|
'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: "database", "eloquent"
|
|
|
|
|
*/
|
|
|
|
'providers' => [
|
|
'users' => [
|
|
'driver' => 'eloquent',
|
|
'model' => env('AUTH_MODEL', 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,
|
|
],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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),
|
|
|
|
];
|