Help with .htaccess

Can anyone tell me how I would hide .htaccess files within Dreamweaver.

My local and remote .htaccess files need to be different for a site I am
working, on so I would like to hide the .htacess files so that I do not
accidentally upload my local .htaccess to my remote site.

I'm working on Dreamweaver 8 on a Mac using OS X 10.4

Thanks

Have you tried cloaking? I'm not sure it would work with .htaccess but it's worth a shot.

Unfortunately, no cloaking might exclude it from site operations, but I still
see it. Normally I'm careful about what I copy up to the remote server, but I
work really late into the night sometimes and worry that I could accidentally
upload it.

"DigitalMirrors" <webforumsuser (AT) macromedia (DOT) com> wrote

Unfortunately, no cloaking might exclude it from site operations, but I
still
see it. Normally I'm careful about what I copy up to the remote server,
but I
work really late into the night sometimes and worry that I could
accidentally
upload it.

Under cloaking put a tick in the box Cloak files ending with and add
..htaccess to the list, works for me on a MBP/Tiger/DW8

--
Dave Buchholz
I-CRE8
www.i-cre8.co.uk
Skype ID: I-CRE8

I've tried that, but the file is still visible which means I could accidentally
upload it if I grabbed a group of files and uploaded.

I'm really looking for a way to stop it from being possible for me to upload
this file. I can't just delete it though because I need it for local testing.

"DigitalMirrors" <webforumsuser (AT) macromedia (DOT) com> wrote

I've tried that, but the file is still visible which means I could
accidentally
upload it if I grabbed a group of files and uploaded.

I'm really looking for a way to stop it from being possible for me to
upload
this file. I can't just delete it though because I need it for local
testing.

Do you at least have a current backup of the .htaccess file on the server?

--
Patty Ayers | Adobe Community Expert
www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate Worksheet
--

yes, I definitely am keeping backups.

This is a really good question and although I don't think I have the answer
you're looking for, I do have a few thoughts on the subject. These are just
ideas off the top of my head as I have not 'solved' this for my own web
development environments..

As far as I know Dreamweaver does not have a standard ability to hide certain
types of files from you in the way you have described.

[hr]
I think that enabling cloaking and cloaking '.htaccess' files is the cleanest,
most DW way to handle the problem. Sure, you might manually upload the file,
but if you're doing your day-to-day work in a DW-like fashion this is a low
probability issue, especially since you are keeping backups of the server side
..htaccess file.

[hr]
You could reconfigure Apache to use standard .htaccess files for the live
environment and use .htaccess-local files for your development environment by
modifying your local httpd.conf file with something similar to this.
AccessFileName .htaccess-local

This Apache configuration command is available in Apache 1.3 and 2 and will
already be protected from prying eyes, in the case of accidental upload, by the
standard <FilesMatch "^\.ht"> rule in your httpd.conf file.

[hr]
You could also try moving the rules from your development .htaccess files into
your main httpd.conf file and using 'AllowOverride None' in the development
environment as well. This way you can keep the .htaccess file in your local DW
tree, have it fall under your existing backup structure/revision control
scheme, and not have a special case to worry about.

[hr]
Another thought, and I'm not actually recommeding this as I have not tried it,
would be to use a single .htaccess file for both environments and use separate
Directory containers for each set of rules. I rarely have the same filesystem
path being used on both the development and live servers. If you have
different filesystem paths you might be able to use Directory container to
server one set of rules for development and another for live.

<Directory /path/to/development/site/files>
Options Includes
</Directory>

<Directory /path/to/live/site/files>
Options Indexes
</Directory>

I will have to consider some of the things you have suggested the .htaccess-local in particular sounds very interesting.

thank you to everyone for you suggestions