Run an HTML based File Manager on the FSG
From OpenFSG
 |
To meet quality standards, this article may require rewriting and/or reformatting. Please help improve this article. The discussion page may contain suggestions. |
In some cases, running a web based file manager can be an asset, especially if you want someone to up and download files through a (corporate) firewall that usually leaves port 80 open but closes other ports.
There are a lot of programms that do this. Take a look at this post about Web file managers for more info.
You can find many of the mentioned programms and more on this page.
Excerpts from the post:
Working on the FSG (FW 3.1.26)
- cjgExplorerPro 3.3
- FileThingie 1.41 (login DOESN'T work!)
- FSGuide 0.7
- PHP Navigator 2
- PHPFileManager 0.2.3
- QuiXplorer 2.3.1
- webadmin 0.9.10
- webfilebrowser 0.4b14
I for one love something at each of them, but none has all the features I'd wish to have available. As I prefer to stay on the safe side of things, I like the best webfilebrowser, which creates a trash bin allowing one to recover accidentally deleted files.
Not working yet
I DIDN'T manage to make some very promising web file managers - maybe you'll be able to do it still (I deleted most of them, this is just what remained on my HDD):
- php_web_commander
- WEBinsta FM Manager 0.1.4
Partially working
And finally there are some apps in this category which work only partially on the FSG (to be more specific: they open the base folder, but are unable to browse any subfolder in it - don't know why):
- Obie FILEMAN 2.0a
- phpCommander 3.0
- webexplorer 2.0
WebFileBrowser
One especially promising is Webfilebrowser
To make it work automagically with the FSG user management system, take a look at the following excerpt from the forum
Starting at line 138 in webFileBrowser.php you have: Code:
//$authmethod = "none"; // Do not require user authentication
//$authmethod = "session"; // Use builtin session-based authentication (recommended, needs the PHP session
// management feature activated)
//$authmethod = "cookie"; // Use builtin cookie-based authentication (not recommended : very basic, very UNSECURE)
//$authmethod = "realm"; // Use builtin browser's basic authentication (needs PHP to be running as a module)
$authmethod = "server"; // Require server based authentication (such as Apache's .htaccess)
As you see above, I have uncommented the last line - that integrates the WFB login with the one of the webserver on the FSG (and it works!).
At line 153 in the same file you have the start of the Profiles definitions.
And at line 199 you should start defining users.
That would be it. It would be probably possible to establish a single common folder and give various users different rights. If you intend to make a sparate folder for each user, FileThingie would be sufficient - although I wonder why don't you use FTP?
I somehow solved the files availability from outside like this: every user has access to his own folder by FTP and all users have access to a common folder by a web file manager - I haven't decided which it will be yet. To make the FTP part easier for any user in any location they might be, I placed a webFTP client on one of my web pages (thus one can avoid using the FTP function of Internet Explorer which has the absolutely idiot habbit to show the username and password in clear in the status bar, while downloading/uploading files (it reads "Opening user:pass@ftp.domain.com..." - anyone could see it!!!).
