Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dotfiles are ignored by 'netlify deploy' #11

Closed
fool opened this issue Sep 15, 2016 · 6 comments
Closed

dotfiles are ignored by 'netlify deploy' #11

fool opened this issue Sep 15, 2016 · 6 comments

Comments

@fool
Copy link
Contributor

fool commented Sep 15, 2016

when you 'netlify deploy' a project that has files or directories beginning with dot ("."), they do not get deployed.
@kirillgroshkov
Copy link

Same here!

@fool
Copy link
Contributor Author

fool commented Jul 2, 2018

This behavior is not limited to our CLI deploys - it is also the case for git-backed deploys. The workaround at present is to use the redirects functionality to serve dotfiles:

/.well-known/* /not-a-dotfile/:splat 200!

Ping support@netlify.com in case you can't get that working.

@kirillgroshkov
Copy link

Yes, support actually helped me today with it by suggesting the same solution. It works!

@bcomnes
Copy link
Contributor

bcomnes commented Aug 27, 2018

We ignore dotfiles except for well-known in the upcoming 2.0.0 release. Please open an issue with your use case if this doesn't work for you.

@bcomnes bcomnes closed this as completed Aug 27, 2018
@thundermiracle thundermiracle mentioned this issue Jun 28, 2019
Closed
@zalnaRs
Copy link

zalnaRs commented Jan 22, 2022

I still have the issue even with this redirect solutions I wanted to use it for trusted web activities which requires an .well-known/assetlinks.json but I can't get it to work so I can access it.

@fool
Copy link
Contributor Author

fool commented Jan 23, 2022

perhaps you could show us your code and tell us what site you are using it on. This should work well if you configure things correctly, but asserting that "i can't get it to work" doesn't help us help you troubleshoot.

PS: I'd suggest opening a community thread at https://answers.netlify.com rather than responding to closed github issues, if you'd like for our Support team to help you, too :)

eduardoboucas added a commit that referenced this issue Apr 18, 2022
@eduardoboucas
feat: generate ETag header (#11)
68adcda 
* chore: change package details

* chore: update package

* chore: bump

* chore: add @netlify/edge-bundler

* chore: bump

* chore: remove npmrc line

* chore: bump version

* chore: update @netlify/edge-bundler

* feat: deploy Edge Handlers to internal path

* feat: add local development experience

* chore: bump version

* chore: update @netlify/edge-bundler

* refactor: move `watcher` util

* feat: add `configWatcher`

* feat: updates to Edge Handlers dev server

* chore: update @netlify/edge-bundler

* refactor: remove unused error binding

* chore: update package name

* chore: update deps

* fix: use correct URL path when matching Edge Handlers

* chore: bump version

* chore: bump version

* feat: add support for internal handlers in local dev (#1)

* feat: add support for internal handlers in local dev

* refactor: correctly merge declarations

* chore: bump version

* fix: run config watcher only on certain commands (#2)

* chore: bump version

* chore: bump version

* feat: add support for user import maps (#3)

* feat: add support for user import maps

* feat: warn when failing to read import map file

* chore: bump version

* chore: bump version

* fix: improve error handling for Edge Handlers (#4)

* chore: bump version

* feat: listen for `NETLIFY_DENO_DEBUG` environment variable (#5)

* feat: listen for `NETLIFY_DENO_DEBUG` environment variable

* chore: upgrade @netlify-labs/edge-bundler

* chore: bump version

* fix: use `0.0.0.0` for Deno server host (#6)

* fix: wait for Edge Handlers server to become available (#7)

* fix: wait for Edge Handlers server to become available

* refactor: wait for server inside request

* refactor: increase timeout

* refactor: use watcher from correct location

* chore: update package.json

* chore: disable release-please

* feat: replace @netlify/build with @netlify-labs/build-internal

* chore: use token in CI

* refactor: use existing config watcher

* chore: remove unused variables

* chore: remove actions

* chore: remove action

* chore: update test

* chore: add tests

* chore: move env to job

* chore: remove duplicate env

* chore: fix tests

* chore: remove unused imports

* fix: check if EH directory exists before deploy

* feat: rename Edge Handlers to Edge Functions (#9)

* chore: fix linting issue

* chore: fix tests

* chore: fix test

* chore: add `withEdgeFunction` test helper

* chore: remove `console.log`

* refactor: remove old Edge Handlers code

* chore: update packages

* fix: remove reference to traffic-mesh

* chore: fix linting issue

* chore: fix linting issue

* refactor: remove unused code

* refactor: remove `dev:trace` command

* chore: setup Deno in the CI

* refactor: use different localhost IP

* chore: simplify test

* chore: simplify test

* feat: generate ETag header

* chore: remove debug statement

* chore: add etag module

* refactor: use `const`

* refactor: make `shouldGenerateETag` a function

* chore: add tests

* chore: use node-fetch in test
@daveaglick daveaglick mentioned this issue Dec 5, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bcomnes @fool @kirillgroshkov @zalnaRs