Sounds simple enough, but this is just an intro post for some other cool PowerShell related posts.
One thing I needed was a WebDav server, and well, why not use my handy little Qube server.
If you want to set up the Apache WebDav module (in this case on NetBSD) simply:
- Ensure you have the apache DAV module installed
- We need a folder for the DavLock database, i did the following:
- Once you have the folders, add the following lines to your http.conf. Note this will assume that the folder webdav is stored wherever the rest of your htdocs are, so you need to make the folder or create a symbolic link from there to where you want WebDav files to be stored.
- Restart/Reload the Apache Service
- DONE!
Notes:
I should probably explain the lines we are entering in the httpd.conf file, as they will cause you some confusion if I don't.
The first line is specifying where we want the DavLockDB, in this case, we want the files to be called DavLock, in the folder we created earlier.
We then have the usual Apache location tags, in this case we want the location to be /webdav. Change this to suit your needs. You could also use Directory tags.
The next three lines are to do with authentication and authorisation. I only ever perform authentication with HTTP Digest (the first line), and I always where possible create a new authentication realm which Apache calls the AuthName. Finally we need to have a list of usernames and passwords, AuthUserFile will point to where we have a file of usernames and passwords setup in the correct method for Apache.
The file section, is something that was covered in the Apache documentation, and to be frank, I don't fully understand as the Apache configuration layout is still perplexing to me. What I know is that this line is limiting who can access the webdav location, in this case, valid-user means anyone who authenticates successfully and isn't a guest will have access. I am sorry I couldn't be any more helpful.
So now we have all of this sorted, I will be able to show you all soon, some of the cool PowerShell stuff I have been investigating. As a teaser, I have been looking at the various was PowerShell can integrate with web applications, as well as new methods for PowerShell to copy and save data that it creates.
I have also been working on some updates to my standard template, minor tweaks in formatting really, as well as some fun stuff around making the copy script I use every day an even more powerful and flexible tool.