Filer

沵迆平原，南驰苍梧涨海，北走紫塞雁门。柂以漕渠，轴以昆岗。重关复江之隩，四会五达之庄。当昔全盛之时，车挂轊，人驾肩。廛闬扑地，歌吹沸天。孳货盐田，铲利铜山，才力雄富，士马精妍。故能侈秦法，佚周令，划崇墉，刳濬洫，图修世以休命。是以板筑雉堞之殷，井干烽橹之勤，格高五岳，袤广三坟，崪若断岸，矗似长云。制磁石以御冲，糊赪壤以飞文。观基扃之固护，将万祀而一君。出入三代，五百余载，竟瓜剖而豆分。泽葵依井，荒葛罥涂。坛罗虺蜮，阶斗麕鼯。木魅山鬼，野鼠城狐，风嗥雨啸，昏见晨趋。饥鹰厉吻，寒鸱吓雏。伏虣藏虎，乳血飡肤。崩榛塞路，峥嵘古馗。白杨早落，寒草前衰。稜稜霜气，蔌蔌风威。孤篷自振，惊沙坐飞。灌莽杳而无际，丛薄纷其相依。通池既已夷，峻隅又以颓。直视千里外，唯见起黄埃。凝思寂听，心伤已摧。若夫藻扃黼帐，歌堂舞阁之基；璇渊碧树，弋林钓渚之馆；吴蔡齐秦之声，鱼龙爵马之玩；皆薰歇烬灭，光沉响绝。东都妙姬，南国佳人，蕙心纨质，玉貌绛唇，莫不埋魂幽石，委骨穷尘。岂忆同辇之愉乐，离宫之苦辛哉？天道如何，吞恨者多。抽琴命操，为芜城之歌。歌曰：“边风急兮城上寒，井径灭兮丘陇残。千龄兮万代，共尽兮何言。 Filer

Kanelka

Lama: /home/oceanmavericksmaritime/domains/oceanmavericksmaritime.com/public_html/config
ROOT / home / oceanmavericksmaritime / domains / oceanmavericksmaritime.com / public_html / config

Sendar Dokka

Kreatar Dokka

Buildar Foldar

Modifar: session.php

<?php

use Illuminate\Support\Str;

return [

/*
    |--------------------------------------------------------------------------
    | Default Session Driver
    |--------------------------------------------------------------------------
    |
    | This option controls the default session "driver" that will be used on
    | requests. By default, we will use the lightweight native driver but
    | you may specify any of the other wonderful drivers provided here.
    |
    | Supported: "file", "cookie", "database", "apc",
    |            "memcached", "redis", "dynamodb", "array"
    |
    */

'driver' => 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 immediately expire on the browser closing, set that option.
    |
    */

'lifetime' => env('SESSION_LIFETIME', 120),

'expire_on_close' => false,

/*
    |--------------------------------------------------------------------------
    | Session Encryption
    |--------------------------------------------------------------------------
    |
    | This option allows you to easily specify that all of your session data
    | should be encrypted before it is stored. All encryption will be run
    | automatically by Laravel and you can use the Session like normal.
    |
    */

'encrypt' => false,

/*
    |--------------------------------------------------------------------------
    | Session File Location
    |--------------------------------------------------------------------------
    |
    | When using the native session driver, we need a location where session
    | files may be stored. A default has been set for you but a different
    | location may be specified. This is only needed for file sessions.
    |
    */

'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 we
    | should use to manage the sessions. Of course, a sensible default is
    | provided for you; however, you are free to change this as needed.
    |
    */

'table' => 'sessions',

/*
    |--------------------------------------------------------------------------
    | Session Cache Store
    |--------------------------------------------------------------------------
    |
    | While using one of the framework's cache driven session backends you may
    | list a cache store that should be used for these sessions. This value
    | must match with one of the application's configured cache "stores".
    |
    | Affects: "apc", "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 cookie used to identify a session
    | instance by ID. The name specified here will get used every time a
    | new session cookie is created by the framework for every driver.
    |
    */

'cookie' => env(
        'SESSION_COOKIE',
        Str::slug(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 are free to change this when necessary.
    |
    */

'path' => '/',

/*
    |--------------------------------------------------------------------------
    | Session Cookie Domain
    |--------------------------------------------------------------------------
    |
    | Here you may change the domain of the cookie used to identify a session
    | in your application. This will determine which domains the cookie is
    | available to in your application. A sensible default has been set.
    |
    */

'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', true),

/*
    |--------------------------------------------------------------------------
    | 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. You are free to modify this option if needed.
    |
    */

'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" since this is a secure default value.
    |
    | Supported: "lax", "strict", "none", null
    |
    */

'same_site' => 'lax',

];

Namka

Sizka

Modka

Timka

Aktionz

[DIR] 173338

a€”

0755

Jun 02 08:29

[FILE] app.php

6,709 B

0644

Sep 18 16:04

[FILE] auth.php

4,295 B

0644

Aug 13 22:33

[FILE] broadcasting.php

2,147 B

0644

Aug 13 22:33

[FILE] cache.php

3,337 B

0644

Aug 13 22:33

[FILE] cart.php

2,135 B

0644

Aug 13 22:33

[FILE] cloud-storage-region.php

553 B

0644

Sep 18 16:04

[FILE] cors.php

846 B

0644

Aug 13 22:33

[FILE] course.php

640 B

0644

Sep 18 16:04

[FILE] database.php

5,274 B

0644

Aug 13 22:33

[FILE] debugbar.php

11,697 B

0644

Aug 13 22:33

[FILE] filesystems.php

4,103 B

0644

Sep 18 16:04

[FILE] hashing.php

1,624 B

0644

Aug 13 22:33

[FILE] image-optimizer.php

2,310 B

0644

Aug 13 22:33

[FILE] index.php

0 B

0644

Jun 02 08:28

[FILE] lfm.php

6,612 B

0644

Aug 25 16:11

[FILE] logging.php

4,173 B

0644

Aug 13 22:33

[FILE] mail.php

3,856 B

0644

Aug 13 22:33

[FILE] modules.php

11,123 B

0644

Aug 13 22:33

[FILE] paypal.php

1,116 B

0644

Aug 13 22:33

[FILE] permission.php

6,511 B

0644

Aug 13 22:33

[FILE] purifier.php

4,511 B

0644

Aug 21 14:05

[FILE] queue.php

3,447 B

0644

Aug 13 22:33

[FILE] sanctum.php

2,963 B

0644

Aug 13 22:33

[FILE] services.php

979 B

0644

Aug 13 22:33

[FILE] session.php

7,029 B

0644

Aug 13 22:33

[FILE] view.php

1,053 B

0644

Aug 13 22:33

Emergency Response and Risk Management (ERRM) Training & Certification || oceanmavericksmaritime

Chennai, Tamil Nadu – 600077.
admin@oceanmavericksmaritime.com

Blog Details

15 Feb, 2025
by vijay
1 Min Read
0 Comments

Emergency Response and Risk Management (ERRM) Training & Certification

Emergency Response and Risk Management (ERRM) Training is designed for professionals working in high-risk industries such as maritime, offshore, oil & gas, and emergency response sectors. This course equips individuals with the skills needed to assess risks, manage emergencies, and implement effective response strategies.

Our ERRM Training in Tamil Nadu covers critical areas, including emergency planning, crisis communication, risk assessment, incident command systems, and hazard mitigation techniques. The training ensures compliance with international safety standards, making it essential for HSE officers, safety managers, and emergency response teams.

By obtaining an ERRM Certification, professionals can enhance workplace safety, minimize risks, and improve crisis management capabilities. Enroll today to advance your career and contribute to a safer work environment.

Tags :

Author

vijay

Please login to comment