|
|
|
(My apologies to all if the HTML still hasn't been turned off.)
While your question applies directly to Unix, it should be noted that the manner in which you can accomplish this on NT is as follows:
In IIS set up a URL (eg. 127.0.0.1) for all stores. In security section of the IIS properties dialogue box, allow all read and script access. Subordinate to that url, create new directories for each new catalog. Treat new catalogues as new clients.
Create an FTP site using the same IP address as above. In security section of IIS, select use Native NT security. Subordinate to that url, create new directories for each new catalog. Treat new catalogues as new clients. This will allow your clients the abiltiy to modify/send-so-your-company-can-import-to-mvned new datafiles. If you don't want them the ability to do this, then don't set up the FTP site and disregard the NT Permission section of this reply.
If you use c:/inetpub/wwwroot/stores as the home directory for this new URL, create a new directory for each new client. eg c:/inetpub/wwwroot/store/<newclient>
Use the same cgi-bin for each client: http://127.0.0.1/cgi-bin will equate to c:/inetpub/wwwroot/store/cgi-bin.
NT Permissions: In User Manager, create a single user account for that client. Then create a new group for each new client. Assign to this group, the webmaster for the client, all administrators, and an administrator group for your company. Using My computer, assign read/write permissions for c:/inetpub/wwwroot/store/<newclient> to this new group.
Run makecat and use these settings for the setup. Note that the makecat.bat file which calls makecat.pm allows for this kind of hierarchal setup. Interestingly, this type of structure should also work in Unix, although some of the terms will be exchanged for thier unix counterparts.
mike
-----Original Message-----
From: John Goerzen [mailto:jgoerzen@southwind.net]
Sent: Thursday, March 18, 1999 12:14 PM
To: minivend-users@minivend.com
Subject: Multiple Minivends on one machine
****** message to minivend-users from John Goerzen <jgoerzen@southwind.net> ******
Hello,
I work for an ISP that would like to offer Minivend for customers that
wish to provide things online. Our setup is: each customer has their
own Unix account, and they cannot read or write to files in other
accounts. We would like to have a site-wide installation of Minivend,
and have only the applicable catalogs and related files stored in each
user's directory. This way, upgrades would hopefully be easier,
resource utilization would be lower because of only one Minivend
daemon running, and disk space requirements would be lower.
However, the documentation doesn't address how to set up Minivend in
this manner. I'm curious as to how one would do that, and secondly,
what security implications there might be. (Ie, if you have access to
configure one catalog, could this be exploited to access a different
catalog?)
Thanks,
John Goerzen
-
To unsubscribe from the list, DO NOT REPLY to this message. Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list