98 |
99 |
100 |
--------------------------------------------------------------------------------
/config/auth.php:
--------------------------------------------------------------------------------
1 | [
17 | 'guard' => 'web',
18 | 'passwords' => 'users',
19 | ],
20 |
21 | /*
22 | |--------------------------------------------------------------------------
23 | | Authentication Guards
24 | |--------------------------------------------------------------------------
25 | |
26 | | Next, you may define every authentication guard for your application.
27 | | Of course, a great default configuration has been defined for you
28 | | here which uses session storage and the Eloquent user provider.
29 | |
30 | | All authentication drivers have a user provider. This defines how the
31 | | users are actually retrieved out of your database or other storage
32 | | mechanisms used by this application to persist your user's data.
33 | |
34 | | Supported: "session", "token"
35 | |
36 | */
37 |
38 | 'guards' => [
39 | 'web' => [
40 | 'driver' => 'session',
41 | 'provider' => 'users',
42 | ],
43 |
44 | 'api' => [
45 | 'driver' => 'token',
46 | 'provider' => 'users',
47 | ],
48 | ],
49 |
50 | /*
51 | |--------------------------------------------------------------------------
52 | | User Providers
53 | |--------------------------------------------------------------------------
54 | |
55 | | All authentication drivers have a user provider. This defines how the
56 | | users are actually retrieved out of your database or other storage
57 | | mechanisms used by this application to persist your user's data.
58 | |
59 | | If you have multiple user tables or models you may configure multiple
60 | | sources which represent each model / table. These sources may then
61 | | be assigned to any extra authentication guards you have defined.
62 | |
63 | | Supported: "database", "eloquent"
64 | |
65 | */
66 |
67 | 'providers' => [
68 | 'users' => [
69 | 'driver' => 'eloquent',
70 | 'model' => App\User::class,
71 | ],
72 |
73 | // 'users' => [
74 | // 'driver' => 'database',
75 | // 'table' => 'users',
76 | // ],
77 | ],
78 |
79 | /*
80 | |--------------------------------------------------------------------------
81 | | Resetting Passwords
82 | |--------------------------------------------------------------------------
83 | |
84 | | You may specify multiple password reset configurations if you have more
85 | | than one user table or model in the application and you want to have
86 | | separate password reset settings based on the specific user types.
87 | |
88 | | The expire time is the number of minutes that the reset token should be
89 | | considered valid. This security feature keeps tokens short-lived so
90 | | they have less time to be guessed. You may change this as needed.
91 | |
92 | */
93 |
94 | 'passwords' => [
95 | 'users' => [
96 | 'provider' => 'users',
97 | 'table' => 'password_resets',
98 | 'expire' => 60,
99 | ],
100 | ],
101 |
102 | ];
103 |
--------------------------------------------------------------------------------
/public/svg/404.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/config/database.php:
--------------------------------------------------------------------------------
1 | env('DB_CONNECTION', 'mysql'),
17 |
18 | /*
19 | |--------------------------------------------------------------------------
20 | | Database Connections
21 | |--------------------------------------------------------------------------
22 | |
23 | | Here are each of the database connections setup for your application.
24 | | Of course, examples of configuring each database platform that is
25 | | supported by Laravel is shown below to make development simple.
26 | |
27 | |
28 | | All database work in Laravel is done through the PHP PDO facilities
29 | | so make sure you have the driver for your particular database of
30 | | choice installed on your machine before you begin development.
31 | |
32 | */
33 |
34 | 'connections' => [
35 |
36 | 'sqlite' => [
37 | 'driver' => 'sqlite',
38 | 'database' => env('DB_DATABASE', database_path('database.sqlite')),
39 | 'prefix' => '',
40 | 'foreign_key_constraints' => env('DB_FOREIGN_KEYS', true),
41 | ],
42 |
43 | 'mysql' => [
44 | 'driver' => 'mysql',
45 | 'host' => env('DB_HOST', '127.0.0.1'),
46 | 'port' => env('DB_PORT', '3306'),
47 | 'database' => env('DB_DATABASE', 'forge'),
48 | 'username' => env('DB_USERNAME', 'forge'),
49 | 'password' => env('DB_PASSWORD', ''),
50 | 'unix_socket' => env('DB_SOCKET', ''),
51 | 'charset' => 'utf8mb4',
52 | 'collation' => 'utf8mb4_unicode_ci',
53 | 'prefix' => '',
54 | 'prefix_indexes' => true,
55 | 'strict' => true,
56 | 'engine' => null,
57 | ],
58 |
59 | 'pgsql' => [
60 | 'driver' => 'pgsql',
61 | 'host' => env('DB_HOST', '127.0.0.1'),
62 | 'port' => env('DB_PORT', '5432'),
63 | 'database' => env('DB_DATABASE', 'forge'),
64 | 'username' => env('DB_USERNAME', 'forge'),
65 | 'password' => env('DB_PASSWORD', ''),
66 | 'charset' => 'utf8',
67 | 'prefix' => '',
68 | 'prefix_indexes' => true,
69 | 'schema' => 'public',
70 | 'sslmode' => 'prefer',
71 | ],
72 |
73 | 'sqlsrv' => [
74 | 'driver' => 'sqlsrv',
75 | 'host' => env('DB_HOST', 'localhost'),
76 | 'port' => env('DB_PORT', '1433'),
77 | 'database' => env('DB_DATABASE', 'forge'),
78 | 'username' => env('DB_USERNAME', 'forge'),
79 | 'password' => env('DB_PASSWORD', ''),
80 | 'charset' => 'utf8',
81 | 'prefix' => '',
82 | 'prefix_indexes' => true,
83 | ],
84 |
85 | ],
86 |
87 | /*
88 | |--------------------------------------------------------------------------
89 | | Migration Repository Table
90 | |--------------------------------------------------------------------------
91 | |
92 | | This table keeps track of all the migrations that have already run for
93 | | your application. Using this information, we can determine which of
94 | | the migrations on disk haven't actually been run in the database.
95 | |
96 | */
97 |
98 | 'migrations' => 'migrations',
99 |
100 | /*
101 | |--------------------------------------------------------------------------
102 | | Redis Databases
103 | |--------------------------------------------------------------------------
104 | |
105 | | Redis is an open source, fast, and advanced key-value store that also
106 | | provides a richer body of commands than a typical key-value system
107 | | such as APC or Memcached. Laravel makes it easy to dig right in.
108 | |
109 | */
110 |
111 | 'redis' => [
112 |
113 | 'client' => 'predis',
114 |
115 | 'default' => [
116 | 'host' => env('REDIS_HOST', '127.0.0.1'),
117 | 'password' => env('REDIS_PASSWORD', null),
118 | 'port' => env('REDIS_PORT', 6379),
119 | 'database' => env('REDIS_DB', 0),
120 | ],
121 |
122 | 'cache' => [
123 | 'host' => env('REDIS_HOST', '127.0.0.1'),
124 | 'password' => env('REDIS_PASSWORD', null),
125 | 'port' => env('REDIS_PORT', 6379),
126 | 'database' => env('REDIS_CACHE_DB', 1),
127 | ],
128 |
129 | ],
130 |
131 | ];
132 |
--------------------------------------------------------------------------------
/config/mail.php:
--------------------------------------------------------------------------------
1 | env('MAIL_DRIVER', 'smtp'),
20 |
21 | /*
22 | |--------------------------------------------------------------------------
23 | | SMTP Host Address
24 | |--------------------------------------------------------------------------
25 | |
26 | | Here you may provide the host address of the SMTP server used by your
27 | | applications. A default option is provided that is compatible with
28 | | the Mailgun mail service which will provide reliable deliveries.
29 | |
30 | */
31 |
32 | 'host' => env('MAIL_HOST', 'smtp.mailgun.org'),
33 |
34 | /*
35 | |--------------------------------------------------------------------------
36 | | SMTP Host Port
37 | |--------------------------------------------------------------------------
38 | |
39 | | This is the SMTP port used by your application to deliver e-mails to
40 | | users of the application. Like the host we have set this value to
41 | | stay compatible with the Mailgun e-mail application by default.
42 | |
43 | */
44 |
45 | 'port' => env('MAIL_PORT', 587),
46 |
47 | /*
48 | |--------------------------------------------------------------------------
49 | | Global "From" Address
50 | |--------------------------------------------------------------------------
51 | |
52 | | You may wish for all e-mails sent by your application to be sent from
53 | | the same address. Here, you may specify a name and address that is
54 | | used globally for all e-mails that are sent by your application.
55 | |
56 | */
57 |
58 | 'from' => [
59 | 'address' => env('MAIL_FROM_ADDRESS', 'hello@example.com'),
60 | 'name' => env('MAIL_FROM_NAME', 'Example'),
61 | ],
62 |
63 | /*
64 | |--------------------------------------------------------------------------
65 | | E-Mail Encryption Protocol
66 | |--------------------------------------------------------------------------
67 | |
68 | | Here you may specify the encryption protocol that should be used when
69 | | the application send e-mail messages. A sensible default using the
70 | | transport layer security protocol should provide great security.
71 | |
72 | */
73 |
74 | 'encryption' => env('MAIL_ENCRYPTION', 'tls'),
75 |
76 | /*
77 | |--------------------------------------------------------------------------
78 | | SMTP Server Username
79 | |--------------------------------------------------------------------------
80 | |
81 | | If your SMTP server requires a username for authentication, you should
82 | | set it here. This will get used to authenticate with your server on
83 | | connection. You may also set the "password" value below this one.
84 | |
85 | */
86 |
87 | 'username' => env('MAIL_USERNAME'),
88 |
89 | 'password' => env('MAIL_PASSWORD'),
90 |
91 | /*
92 | |--------------------------------------------------------------------------
93 | | Sendmail System Path
94 | |--------------------------------------------------------------------------
95 | |
96 | | When using the "sendmail" driver to send e-mails, we will need to know
97 | | the path to where Sendmail lives on this server. A default path has
98 | | been provided here, which will work well on most of your systems.
99 | |
100 | */
101 |
102 | 'sendmail' => '/usr/sbin/sendmail -bs',
103 |
104 | /*
105 | |--------------------------------------------------------------------------
106 | | Markdown Mail Settings
107 | |--------------------------------------------------------------------------
108 | |
109 | | If you are using Markdown based email rendering, you may configure your
110 | | theme and component paths here, allowing you to customize the design
111 | | of the emails. Or, you may simply stick with the Laravel defaults!
112 | |
113 | */
114 |
115 | 'markdown' => [
116 | 'theme' => 'default',
117 |
118 | 'paths' => [
119 | resource_path('views/vendor/mail'),
120 | ],
121 | ],
122 |
123 | /*
124 | |--------------------------------------------------------------------------
125 | | Log Channel
126 | |--------------------------------------------------------------------------
127 | |
128 | | If you are using the "log" driver, you may specify the logging channel
129 | | if you prefer to keep mail messages separate from other log entries
130 | | for simpler reading. Otherwise, the default channel will be used.
131 | |
132 | */
133 |
134 | 'log_channel' => env('MAIL_LOG_CHANNEL'),
135 |
136 | ];
137 |
--------------------------------------------------------------------------------
/public/svg/503.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/public/svg/403.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/config/session.php:
--------------------------------------------------------------------------------
1 | env('SESSION_DRIVER', 'file'),
22 |
23 | /*
24 | |--------------------------------------------------------------------------
25 | | Session Lifetime
26 | |--------------------------------------------------------------------------
27 | |
28 | | Here you may specify the number of minutes that you wish the session
29 | | to be allowed to remain idle before it expires. If you want them
30 | | to immediately expire on the browser closing, set that option.
31 | |
32 | */
33 |
34 | 'lifetime' => env('SESSION_LIFETIME', 120),
35 |
36 | 'expire_on_close' => false,
37 |
38 | /*
39 | |--------------------------------------------------------------------------
40 | | Session Encryption
41 | |--------------------------------------------------------------------------
42 | |
43 | | This option allows you to easily specify that all of your session data
44 | | should be encrypted before it is stored. All encryption will be run
45 | | automatically by Laravel and you can use the Session like normal.
46 | |
47 | */
48 |
49 | 'encrypt' => false,
50 |
51 | /*
52 | |--------------------------------------------------------------------------
53 | | Session File Location
54 | |--------------------------------------------------------------------------
55 | |
56 | | When using the native session driver, we need a location where session
57 | | files may be stored. A default has been set for you but a different
58 | | location may be specified. This is only needed for file sessions.
59 | |
60 | */
61 |
62 | 'files' => storage_path('framework/sessions'),
63 |
64 | /*
65 | |--------------------------------------------------------------------------
66 | | Session Database Connection
67 | |--------------------------------------------------------------------------
68 | |
69 | | When using the "database" or "redis" session drivers, you may specify a
70 | | connection that should be used to manage these sessions. This should
71 | | correspond to a connection in your database configuration options.
72 | |
73 | */
74 |
75 | 'connection' => env('SESSION_CONNECTION', null),
76 |
77 | /*
78 | |--------------------------------------------------------------------------
79 | | Session Database Table
80 | |--------------------------------------------------------------------------
81 | |
82 | | When using the "database" session driver, you may specify the table we
83 | | should use to manage the sessions. Of course, a sensible default is
84 | | provided for you; however, you are free to change this as needed.
85 | |
86 | */
87 |
88 | 'table' => 'sessions',
89 |
90 | /*
91 | |--------------------------------------------------------------------------
92 | | Session Cache Store
93 | |--------------------------------------------------------------------------
94 | |
95 | | When using the "apc" or "memcached" session drivers, you may specify a
96 | | cache store that should be used for these sessions. This value must
97 | | correspond with one of the application's configured cache stores.
98 | |
99 | */
100 |
101 | 'store' => env('SESSION_STORE', null),
102 |
103 | /*
104 | |--------------------------------------------------------------------------
105 | | Session Sweeping Lottery
106 | |--------------------------------------------------------------------------
107 | |
108 | | Some session drivers must manually sweep their storage location to get
109 | | rid of old sessions from storage. Here are the chances that it will
110 | | happen on a given request. By default, the odds are 2 out of 100.
111 | |
112 | */
113 |
114 | 'lottery' => [2, 100],
115 |
116 | /*
117 | |--------------------------------------------------------------------------
118 | | Session Cookie Name
119 | |--------------------------------------------------------------------------
120 | |
121 | | Here you may change the name of the cookie used to identify a session
122 | | instance by ID. The name specified here will get used every time a
123 | | new session cookie is created by the framework for every driver.
124 | |
125 | */
126 |
127 | 'cookie' => env(
128 | 'SESSION_COOKIE',
129 | Str::slug(env('APP_NAME', 'laravel'), '_').'_session'
130 | ),
131 |
132 | /*
133 | |--------------------------------------------------------------------------
134 | | Session Cookie Path
135 | |--------------------------------------------------------------------------
136 | |
137 | | The session cookie path determines the path for which the cookie will
138 | | be regarded as available. Typically, this will be the root path of
139 | | your application but you are free to change this when necessary.
140 | |
141 | */
142 |
143 | 'path' => '/',
144 |
145 | /*
146 | |--------------------------------------------------------------------------
147 | | Session Cookie Domain
148 | |--------------------------------------------------------------------------
149 | |
150 | | Here you may change the domain of the cookie used to identify a session
151 | | in your application. This will determine which domains the cookie is
152 | | available to in your application. A sensible default has been set.
153 | |
154 | */
155 |
156 | 'domain' => env('SESSION_DOMAIN', null),
157 |
158 | /*
159 | |--------------------------------------------------------------------------
160 | | HTTPS Only Cookies
161 | |--------------------------------------------------------------------------
162 | |
163 | | By setting this option to true, session cookies will only be sent back
164 | | to the server if the browser has a HTTPS connection. This will keep
165 | | the cookie from being sent to you if it can not be done securely.
166 | |
167 | */
168 |
169 | 'secure' => env('SESSION_SECURE_COOKIE', false),
170 |
171 | /*
172 | |--------------------------------------------------------------------------
173 | | HTTP Access Only
174 | |--------------------------------------------------------------------------
175 | |
176 | | Setting this value to true will prevent JavaScript from accessing the
177 | | value of the cookie and the cookie will only be accessible through
178 | | the HTTP protocol. You are free to modify this option if needed.
179 | |
180 | */
181 |
182 | 'http_only' => true,
183 |
184 | /*
185 | |--------------------------------------------------------------------------
186 | | Same-Site Cookies
187 | |--------------------------------------------------------------------------
188 | |
189 | | This option determines how your cookies behave when cross-site requests
190 | | take place, and can be used to mitigate CSRF attacks. By default, we
191 | | do not enable this as other CSRF protection services are in place.
192 | |
193 | | Supported: "lax", "strict"
194 | |
195 | */
196 |
197 | 'same_site' => null,
198 |
199 | ];
200 |
--------------------------------------------------------------------------------
/resources/lang/en/validation.php:
--------------------------------------------------------------------------------
1 | 'The :attribute must be accepted.',
17 | 'active_url' => 'The :attribute is not a valid URL.',
18 | 'after' => 'The :attribute must be a date after :date.',
19 | 'after_or_equal' => 'The :attribute must be a date after or equal to :date.',
20 | 'alpha' => 'The :attribute may only contain letters.',
21 | 'alpha_dash' => 'The :attribute may only contain letters, numbers, dashes and underscores.',
22 | 'alpha_num' => 'The :attribute may only contain letters and numbers.',
23 | 'array' => 'The :attribute must be an array.',
24 | 'before' => 'The :attribute must be a date before :date.',
25 | 'before_or_equal' => 'The :attribute must be a date before or equal to :date.',
26 | 'between' => [
27 | 'numeric' => 'The :attribute must be between :min and :max.',
28 | 'file' => 'The :attribute must be between :min and :max kilobytes.',
29 | 'string' => 'The :attribute must be between :min and :max characters.',
30 | 'array' => 'The :attribute must have between :min and :max items.',
31 | ],
32 | 'boolean' => 'The :attribute field must be true or false.',
33 | 'confirmed' => 'The :attribute confirmation does not match.',
34 | 'date' => 'The :attribute is not a valid date.',
35 | 'date_equals' => 'The :attribute must be a date equal to :date.',
36 | 'date_format' => 'The :attribute does not match the format :format.',
37 | 'different' => 'The :attribute and :other must be different.',
38 | 'digits' => 'The :attribute must be :digits digits.',
39 | 'digits_between' => 'The :attribute must be between :min and :max digits.',
40 | 'dimensions' => 'The :attribute has invalid image dimensions.',
41 | 'distinct' => 'The :attribute field has a duplicate value.',
42 | 'email' => 'The :attribute must be a valid email address.',
43 | 'exists' => 'The selected :attribute is invalid.',
44 | 'file' => 'The :attribute must be a file.',
45 | 'filled' => 'The :attribute field must have a value.',
46 | 'gt' => [
47 | 'numeric' => 'The :attribute must be greater than :value.',
48 | 'file' => 'The :attribute must be greater than :value kilobytes.',
49 | 'string' => 'The :attribute must be greater than :value characters.',
50 | 'array' => 'The :attribute must have more than :value items.',
51 | ],
52 | 'gte' => [
53 | 'numeric' => 'The :attribute must be greater than or equal :value.',
54 | 'file' => 'The :attribute must be greater than or equal :value kilobytes.',
55 | 'string' => 'The :attribute must be greater than or equal :value characters.',
56 | 'array' => 'The :attribute must have :value items or more.',
57 | ],
58 | 'image' => 'The :attribute must be an image.',
59 | 'in' => 'The selected :attribute is invalid.',
60 | 'in_array' => 'The :attribute field does not exist in :other.',
61 | 'integer' => 'The :attribute must be an integer.',
62 | 'ip' => 'The :attribute must be a valid IP address.',
63 | 'ipv4' => 'The :attribute must be a valid IPv4 address.',
64 | 'ipv6' => 'The :attribute must be a valid IPv6 address.',
65 | 'json' => 'The :attribute must be a valid JSON string.',
66 | 'lt' => [
67 | 'numeric' => 'The :attribute must be less than :value.',
68 | 'file' => 'The :attribute must be less than :value kilobytes.',
69 | 'string' => 'The :attribute must be less than :value characters.',
70 | 'array' => 'The :attribute must have less than :value items.',
71 | ],
72 | 'lte' => [
73 | 'numeric' => 'The :attribute must be less than or equal :value.',
74 | 'file' => 'The :attribute must be less than or equal :value kilobytes.',
75 | 'string' => 'The :attribute must be less than or equal :value characters.',
76 | 'array' => 'The :attribute must not have more than :value items.',
77 | ],
78 | 'max' => [
79 | 'numeric' => 'The :attribute may not be greater than :max.',
80 | 'file' => 'The :attribute may not be greater than :max kilobytes.',
81 | 'string' => 'The :attribute may not be greater than :max characters.',
82 | 'array' => 'The :attribute may not have more than :max items.',
83 | ],
84 | 'mimes' => 'The :attribute must be a file of type: :values.',
85 | 'mimetypes' => 'The :attribute must be a file of type: :values.',
86 | 'min' => [
87 | 'numeric' => 'The :attribute must be at least :min.',
88 | 'file' => 'The :attribute must be at least :min kilobytes.',
89 | 'string' => 'The :attribute must be at least :min characters.',
90 | 'array' => 'The :attribute must have at least :min items.',
91 | ],
92 | 'not_in' => 'The selected :attribute is invalid.',
93 | 'not_regex' => 'The :attribute format is invalid.',
94 | 'numeric' => 'The :attribute must be a number.',
95 | 'present' => 'The :attribute field must be present.',
96 | 'regex' => 'The :attribute format is invalid.',
97 | 'required' => 'The :attribute field is required.',
98 | 'required_if' => 'The :attribute field is required when :other is :value.',
99 | 'required_unless' => 'The :attribute field is required unless :other is in :values.',
100 | 'required_with' => 'The :attribute field is required when :values is present.',
101 | 'required_with_all' => 'The :attribute field is required when :values are present.',
102 | 'required_without' => 'The :attribute field is required when :values is not present.',
103 | 'required_without_all' => 'The :attribute field is required when none of :values are present.',
104 | 'same' => 'The :attribute and :other must match.',
105 | 'size' => [
106 | 'numeric' => 'The :attribute must be :size.',
107 | 'file' => 'The :attribute must be :size kilobytes.',
108 | 'string' => 'The :attribute must be :size characters.',
109 | 'array' => 'The :attribute must contain :size items.',
110 | ],
111 | 'starts_with' => 'The :attribute must start with one of the following: :values',
112 | 'string' => 'The :attribute must be a string.',
113 | 'timezone' => 'The :attribute must be a valid zone.',
114 | 'unique' => 'The :attribute has already been taken.',
115 | 'uploaded' => 'The :attribute failed to upload.',
116 | 'url' => 'The :attribute format is invalid.',
117 | 'uuid' => 'The :attribute must be a valid UUID.',
118 |
119 | /*
120 | |--------------------------------------------------------------------------
121 | | Custom Validation Language Lines
122 | |--------------------------------------------------------------------------
123 | |
124 | | Here you may specify custom validation messages for attributes using the
125 | | convention "attribute.rule" to name the lines. This makes it quick to
126 | | specify a specific custom language line for a given attribute rule.
127 | |
128 | */
129 |
130 | 'custom' => [
131 | 'attribute-name' => [
132 | 'rule-name' => 'custom-message',
133 | ],
134 | ],
135 |
136 | /*
137 | |--------------------------------------------------------------------------
138 | | Custom Validation Attributes
139 | |--------------------------------------------------------------------------
140 | |
141 | | The following language lines are used to swap our attribute placeholder
142 | | with something more reader friendly such as "E-Mail Address" instead
143 | | of "email". This simply helps us make our message more expressive.
144 | |
145 | */
146 |
147 | 'attributes' => [],
148 |
149 | ];
150 |
--------------------------------------------------------------------------------
/config/app.php:
--------------------------------------------------------------------------------
1 | env('APP_NAME', 'Laravel'),
17 |
18 | /*
19 | |--------------------------------------------------------------------------
20 | | Application Environment
21 | |--------------------------------------------------------------------------
22 | |
23 | | This value determines the "environment" your application is currently
24 | | running in. This may determine how you prefer to configure various
25 | | services the application utilizes. Set this in your ".env" file.
26 | |
27 | */
28 |
29 | 'env' => env('APP_ENV', 'production'),
30 |
31 | /*
32 | |--------------------------------------------------------------------------
33 | | Application Debug Mode
34 | |--------------------------------------------------------------------------
35 | |
36 | | When your application is in debug mode, detailed error messages with
37 | | stack traces will be shown on every error that occurs within your
38 | | application. If disabled, a simple generic error page is shown.
39 | |
40 | */
41 |
42 | 'debug' => env('APP_DEBUG', false),
43 |
44 | /*
45 | |--------------------------------------------------------------------------
46 | | Application URL
47 | |--------------------------------------------------------------------------
48 | |
49 | | This URL is used by the console to properly generate URLs when using
50 | | the Artisan command line tool. You should set this to the root of
51 | | your application so that it is used when running Artisan tasks.
52 | |
53 | */
54 |
55 | 'url' => env('APP_URL', 'http://localhost'),
56 |
57 | 'asset_url' => env('ASSET_URL', null),
58 |
59 | /*
60 | |--------------------------------------------------------------------------
61 | | Application Timezone
62 | |--------------------------------------------------------------------------
63 | |
64 | | Here you may specify the default timezone for your application, which
65 | | will be used by the PHP date and date-time functions. We have gone
66 | | ahead and set this to a sensible default for you out of the box.
67 | |
68 | */
69 |
70 | 'timezone' => 'UTC',
71 |
72 | /*
73 | |--------------------------------------------------------------------------
74 | | Application Locale Configuration
75 | |--------------------------------------------------------------------------
76 | |
77 | | The application locale determines the default locale that will be used
78 | | by the translation service provider. You are free to set this value
79 | | to any of the locales which will be supported by the application.
80 | |
81 | */
82 |
83 | 'locale' => 'en',
84 |
85 | /*
86 | |--------------------------------------------------------------------------
87 | | Application Fallback Locale
88 | |--------------------------------------------------------------------------
89 | |
90 | | The fallback locale determines the locale to use when the current one
91 | | is not available. You may change the value to correspond to any of
92 | | the language folders that are provided through your application.
93 | |
94 | */
95 |
96 | 'fallback_locale' => 'en',
97 |
98 | /*
99 | |--------------------------------------------------------------------------
100 | | Faker Locale
101 | |--------------------------------------------------------------------------
102 | |
103 | | This locale will be used by the Faker PHP library when generating fake
104 | | data for your database seeds. For example, this will be used to get
105 | | localized telephone numbers, street address information and more.
106 | |
107 | */
108 |
109 | 'faker_locale' => 'en_US',
110 |
111 | /*
112 | |--------------------------------------------------------------------------
113 | | Encryption Key
114 | |--------------------------------------------------------------------------
115 | |
116 | | This key is used by the Illuminate encrypter service and should be set
117 | | to a random, 32 character string, otherwise these encrypted strings
118 | | will not be safe. Please do this before deploying an application!
119 | |
120 | */
121 |
122 | 'key' => env('APP_KEY'),
123 |
124 | 'cipher' => 'AES-256-CBC',
125 |
126 | /*
127 | |--------------------------------------------------------------------------
128 | | Autoloaded Service Providers
129 | |--------------------------------------------------------------------------
130 | |
131 | | The service providers listed here will be automatically loaded on the
132 | | request to your application. Feel free to add your own services to
133 | | this array to grant expanded functionality to your applications.
134 | |
135 | */
136 |
137 | 'providers' => [
138 |
139 | /*
140 | * Laravel Framework Service Providers...
141 | */
142 | Illuminate\Auth\AuthServiceProvider::class,
143 | Illuminate\Broadcasting\BroadcastServiceProvider::class,
144 | Illuminate\Bus\BusServiceProvider::class,
145 | Illuminate\Cache\CacheServiceProvider::class,
146 | Illuminate\Foundation\Providers\ConsoleSupportServiceProvider::class,
147 | Illuminate\Cookie\CookieServiceProvider::class,
148 | Illuminate\Database\DatabaseServiceProvider::class,
149 | Illuminate\Encryption\EncryptionServiceProvider::class,
150 | Illuminate\Filesystem\FilesystemServiceProvider::class,
151 | Illuminate\Foundation\Providers\FoundationServiceProvider::class,
152 | Illuminate\Hashing\HashServiceProvider::class,
153 | Illuminate\Mail\MailServiceProvider::class,
154 | Illuminate\Notifications\NotificationServiceProvider::class,
155 | Illuminate\Pagination\PaginationServiceProvider::class,
156 | Illuminate\Pipeline\PipelineServiceProvider::class,
157 | Illuminate\Queue\QueueServiceProvider::class,
158 | Illuminate\Redis\RedisServiceProvider::class,
159 | Illuminate\Auth\Passwords\PasswordResetServiceProvider::class,
160 | Illuminate\Session\SessionServiceProvider::class,
161 | Illuminate\Translation\TranslationServiceProvider::class,
162 | Illuminate\Validation\ValidationServiceProvider::class,
163 | Illuminate\View\ViewServiceProvider::class,
164 |
165 | /*
166 | * Package Service Providers...
167 | */
168 |
169 | /*
170 | * Application Service Providers...
171 | */
172 | App\Providers\AppServiceProvider::class,
173 | App\Providers\AuthServiceProvider::class,
174 | // App\Providers\BroadcastServiceProvider::class,
175 | App\Providers\EventServiceProvider::class,
176 | App\Providers\RouteServiceProvider::class,
177 |
178 | ],
179 |
180 | /*
181 | |--------------------------------------------------------------------------
182 | | Class Aliases
183 | |--------------------------------------------------------------------------
184 | |
185 | | This array of class aliases will be registered when this application
186 | | is started. However, feel free to register as many as you wish as
187 | | the aliases are "lazy" loaded so they don't hinder performance.
188 | |
189 | */
190 |
191 | 'aliases' => [
192 |
193 | 'App' => Illuminate\Support\Facades\App::class,
194 | 'Artisan' => Illuminate\Support\Facades\Artisan::class,
195 | 'Auth' => Illuminate\Support\Facades\Auth::class,
196 | 'Blade' => Illuminate\Support\Facades\Blade::class,
197 | 'Broadcast' => Illuminate\Support\Facades\Broadcast::class,
198 | 'Bus' => Illuminate\Support\Facades\Bus::class,
199 | 'Cache' => Illuminate\Support\Facades\Cache::class,
200 | 'Config' => Illuminate\Support\Facades\Config::class,
201 | 'Cookie' => Illuminate\Support\Facades\Cookie::class,
202 | 'Crypt' => Illuminate\Support\Facades\Crypt::class,
203 | 'DB' => Illuminate\Support\Facades\DB::class,
204 | 'Eloquent' => Illuminate\Database\Eloquent\Model::class,
205 | 'Event' => Illuminate\Support\Facades\Event::class,
206 | 'File' => Illuminate\Support\Facades\File::class,
207 | 'Gate' => Illuminate\Support\Facades\Gate::class,
208 | 'Hash' => Illuminate\Support\Facades\Hash::class,
209 | 'Lang' => Illuminate\Support\Facades\Lang::class,
210 | 'Log' => Illuminate\Support\Facades\Log::class,
211 | 'Mail' => Illuminate\Support\Facades\Mail::class,
212 | 'Notification' => Illuminate\Support\Facades\Notification::class,
213 | 'Password' => Illuminate\Support\Facades\Password::class,
214 | 'Queue' => Illuminate\Support\Facades\Queue::class,
215 | 'Redirect' => Illuminate\Support\Facades\Redirect::class,
216 | 'Redis' => Illuminate\Support\Facades\Redis::class,
217 | 'Request' => Illuminate\Support\Facades\Request::class,
218 | 'Response' => Illuminate\Support\Facades\Response::class,
219 | 'Route' => Illuminate\Support\Facades\Route::class,
220 | 'Schema' => Illuminate\Support\Facades\Schema::class,
221 | 'Session' => Illuminate\Support\Facades\Session::class,
222 | 'Storage' => Illuminate\Support\Facades\Storage::class,
223 | 'URL' => Illuminate\Support\Facades\URL::class,
224 | 'Validator' => Illuminate\Support\Facades\Validator::class,
225 | 'View' => Illuminate\Support\Facades\View::class,
226 |
227 | ],
228 |
229 | ];
230 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Run Selenium Tests With Laravel On LambdaTest
2 |
3 | 
4 |
5 |
18 |
19 |
20 |
21 |
22 | *Learn how to use Laravel framework to configure and run your PHP automation scripts on the LambdaTest platform*
23 |
24 | [](https://accounts.lambdatest.com/register?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo)
25 |
26 | ## Table Of Contents
27 |
28 | * [Pre-requisites](#pre-requisites)
29 | * [Run Your First Test](#run-your-first-test)
30 | * [Local Testing With Laravel](#testing-locally-hosted-or-privately-hosted-projects)
31 |
32 |
33 | ## Prerequisites
34 |
35 | Before you begin automation testing with Laravel Dusk, you would need to:
36 |
37 | * Download **PHP v7.4**. You can download and install **PHP** using following commands in the terminal:
38 |
39 | * **MacOS:** Previous versions of **MacOS** have **PHP** installed by default. But for the latest **MacOS** versions starting with **Monterey**, **PHP** has to be downloaded and installed manually by using below commands:
40 | ```bash
41 | /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
42 | brew install php
43 | ```
44 | * **Windows:**
45 | ```bash
46 | sudo apt-get install curl libcurl3 libcurl3-dev php
47 | ```
48 | **Note:** For **Windows**, you can download **PHP** from [here](http://windows.php.net/download/). Also, refer to this [documentation](http://php.net/manual/en/install.windows.php) for ensuring the accessibility of PHP through Command Prompt(cmd).
49 |
50 | You can change the **PHP** version to **7.1** by using below homebrew commands in the terminal:
51 | ```bash
52 | brew unlink php && brew link --force php@7.4
53 | ```
54 | **Note:** You need to download **PHP v7.1** inorder to link to that version.
55 |
56 | * Download **composer** in the project directory ([Linux/MacOS](https://getcomposer.org/download/), [Windows](https://getcomposer.org/doc/00-intro.md#installation-windows)).
57 |
58 | **Note:** To use the **composer** command directly, it either should have been downloaded in the project directory or should be accessible globally which can be done by the command below:
59 |
60 | ```bash
61 | mv composer.phar /usr/local/bin/composer
62 | ```
63 |
64 | ### Installing Selenium Dependencies And Tutorial Repo
65 |
66 | **Step 1:** Clone the LambdaTest’s php-laravel-dusk-todo and navigate to the code directory as shown below:
67 |
68 | ```bash
69 | git clone https://github.com/LambdaTest/php-laravel-dusk-todo
70 | cd php-laravel-dusk-todo
71 | ```
72 | **Step 2:** Install the composer dependencies in the current project directory using the commands below:
73 | ```bash
74 | composer install
75 | composer dump-autoload
76 | ```
77 | if ```composer install``` doesn't work try ```composer update --ignore-platform-reqs```
78 | ### Setting Up Your Authentication
79 |
80 | Make sure you have your LambdaTest credentials with you to run test automation scripts on LambdaTest Selenium Grid. You can obtain these credentials from the [LambdaTest Automation Dashboard](https://automation.lambdatest.com/build?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo) or through [LambdaTest Profile](https://accounts.lambdatest.com/login?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo).
81 |
82 | **Step 3:** Create .env from example file
83 | ```bash
84 | cp .env.example .env
85 | ```
86 |
87 | **Step 4:** You would have to update your LambdaTest credentials in the newly created .env file.
88 |
89 | ```bash
90 | LT_USERNAME=""
91 | LT_ACCESS_KEY="**Test Scenario**: The sample TodoTest.php file tests a sample to-do list app by marking couple items as done, adding a new item to the list and finally displaying the count of pending items as output.
108 |
109 |
110 | **Step 6:** In [DuskTestCase.php](https://github.com/LambdaTest/php-laravel-dusk-todo/blob/master/tests/DuskTestCase.php), we are passing browser, browser version, and operating system information, along with LambdaTest Selenium grid capabilities via capabilities object. Update platform configuration in driver method of `tests/DuskTestCase.php`, to specify the target where tests should run. The capabilities object in the above code are defined as:
111 |
112 | You can generate capabilities for your test requirements with the help of our inbuilt [Desired Capability Generator](https://www.lambdatest.com/capabilities-generator/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo).
113 |
114 | ### Executing The Test
115 |
116 | **Step 7**: The tests can be executed in the terminal using the following command:
117 |
118 | ```bash
119 | php artisan dusk
120 | ```
121 |
122 |
123 | ### Generate Test Cases
124 |
125 | * Change directory to the project root: `cd /your/project`
126 |
127 | * To generate the test cases, you need to execute the following command:
128 | *
129 | `php artisan dusk:make {test case name}`.
130 |
131 | An example for the same is shown below:
132 |
133 | ```bash
134 | php artisan dusk:make TodoTest
135 | ```
136 |
137 | Our sample test case can be found in [TodoTest.php](https://github.com/LambdaTest/php-laravel-dusk-todo/blob/master/tests/Browser/TodoTest.php) file.
138 |
139 | ## Testing Locally Hosted Or Privately Hosted Projects
140 |
141 | You can test your locally hosted or privately hosted projects with LambdaTest Selenium grid using LambdaTest Tunnel. All you would have to do is set up an SSH tunnel using tunnel and pass toggle `tunnel = True` via desired capabilities. LambdaTest Tunnel establishes a secure SSH protocol based tunnel that allows you in testing your locally hosted or privately hosted pages, even before they are live.
142 |
143 | Refer our [LambdaTest Tunnel documentation](https://www.lambdatest.com/support/docs/testing-locally-hosted-pages/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo) for more information.
144 |
145 | Here’s how you can establish LambdaTest Tunnel.
146 |
147 | Download the binary file of:
148 | * [LambdaTest Tunnel for Windows](https://downloads.lambdatest.com/tunnel/v3/windows/64bit/LT_Windows.zip)
149 | * [LambdaTest Tunnel for macOS](https://downloads.lambdatest.com/tunnel/v3/mac/64bit/LT_Mac.zip)
150 | * [LambdaTest Tunnel for Linux](https://downloads.lambdatest.com/tunnel/v3/linux/64bit/LT_Linux.zip)
151 |
152 | Open command prompt and navigate to the binary folder.
153 |
154 | Run the following command:
155 |
156 | ```bash
157 | LT -user {user’s login email} -key {user’s access key}
158 | ```
159 | So if your user name is lambdatest@example.com and key is 123456, the command would be:
160 |
161 | ```bash
162 | LT -user lambdatest@example.com -key 123456
163 | ```
164 | Once you are able to connect **LambdaTest Tunnel** successfully, you would just have to pass on tunnel capabilities in the code shown below :
165 |
166 | **Tunnel Capability**
167 |
168 | ```
169 | "tunnel" => true
170 | ```
171 |
172 | ## Documentation & Resources :books:
173 |
174 |
175 | Visit the following links to learn more about LambdaTest's features, setup and tutorials around test automation, mobile app testing, responsive testing, and manual testing.
176 |
177 | * [LambdaTest Documentation](https://www.lambdatest.com/support/docs/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo)
178 | * [LambdaTest Blog](https://www.lambdatest.com/blog/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo)
179 | * [LambdaTest Learning Hub](https://www.lambdatest.com/learning-hub/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo)
180 |
181 | ## LambdaTest Community :busts_in_silhouette:
182 |
183 | The [LambdaTest Community](https://community.lambdatest.com/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo) allows people to interact with tech enthusiasts. Connect, ask questions, and learn from tech-savvy people. Discuss best practises in web development, testing, and DevOps with professionals from across the globe 🌎
184 |
185 | ## What's New At LambdaTest ❓
186 |
187 | To stay updated with the latest features and product add-ons, visit [Changelog](https://changelog.lambdatest.com/)
188 |
189 | ## About LambdaTest
190 |
191 | [LambdaTest](https://www.lambdatest.com/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo) is a leading test execution and orchestration platform that is fast, reliable, scalable, and secure. It allows users to run both manual and automated testing of web and mobile apps across 3000+ different browsers, operating systems, and real device combinations. Using LambdaTest, businesses can ensure quicker developer feedback and hence achieve faster go to market. Over 500 enterprises and 1 Million + users across 130+ countries rely on LambdaTest for their testing needs.
192 |
193 | ### Features
194 |
195 | * Run Selenium, Cypress, Puppeteer, Playwright, and Appium automation tests across 3000+ real desktop and mobile environments.
196 | * Real-time cross browser testing on 3000+ environments.
197 | * Test on Real device cloud
198 | * Blazing fast test automation with HyperExecute
199 | * Accelerate testing, shorten job times and get faster feedback on code changes with Test At Scale.
200 | * Smart Visual Regression Testing on cloud
201 | * 120+ third-party integrations with your favorite tool for CI/CD, Project Management, Codeless Automation, and more.
202 | * Automated Screenshot testing across multiple browsers in a single click.
203 | * Local testing of web and mobile apps.
204 | * Online Accessibility Testing across 3000+ desktop and mobile browsers, browser versions, and operating systems.
205 | * Geolocation testing of web and mobile apps across 53+ countries.
206 | * LT Browser - for responsive testing across 50+ pre-installed mobile, tablets, desktop, and laptop viewports
207 |
208 |
209 | [](https://accounts.lambdatest.com/register?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo)
210 |
211 | ## We are here to help you :headphones:
212 |
213 | * Got a query? we are available 24x7 to help. [Contact Us](mailto:support@lambdatest.com)
214 | * For more info, visit - [LambdaTest](https://www.lambdatest.com/?utm_source=github&utm_medium=repo&utm_campaign=php-laravel-dusk-todo)
215 |
--------------------------------------------------------------------------------
/public/svg/500.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------