NGINX Directory Browse Configuration on Windows

NGINX is a great web engine and very easy to get started with. In case you need to share files or make them available trough a web interface, all you need to do this, download the latest version of nginx and run it! It's that simple...

For a particular case, I needed to make some folders on my windows machine available so I could share these folder structures on the network (usually I use SMB shares with specific permissions but this was a particular case, don't ask why :) )

The Nginx configuration sits in the "conf" folder when
you download nginx and the file is called, "nginx.conf". Here you can set any specific settings that you want to apply to your nginx web server. For the purpose of my needs, I wanted to allow directory browsing to specific folder and sub-folders on my computer and all I had to do was include the below code in my configuration file.

        location /shared {
            alias "C:/tech/shared";
            autoindex on;
        }

So my configuration looked something like this;


Once the nginx started, I was able to browse http://x.x.x.x:8080/shared url and see all my directories under C:\tech\shared folder.






Location: Montreal, QC, Canada

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more