Skip to content

connect example .env file exposed (!) - include a .htaccess to hide deny #403

Description

@yosun

I like the web js flow that makes payment easy (so that indie devs can focus on building the main app logic), but it seems that if someone quickly deploys, the .env file is exposed. Please include a default .htaccess that protects the env file

.htaccess

# Disable index view
Options -Indexes

# Hide a specific file
<Files .env>
    Order allow,deny
    Deny from all
</Files>

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions