SOLVED: Re: [mv] Running 2 Diffrent MiniVend on Same Server

[Marius Schaefer <maillist@b-p-a.com>]

******    message to minivend-users from Marius Schaefer <maillist@b-p-a.com>     ******

Hi,

> > > I've you running inet mode, you should define different ports in
> > > minivend.cfg.
> >
> > If I do this, the change of the port in minivend.cfg has no effect (both
> > access 7786). Could it be that I have to define something _before_
> > tlink/vlink is created?
> 
> I do not know, on which OS and webserver is the both MV running. I
> believe, the webserver has to listen the port and the webserver has to
> know, which number has the webserver to listen. Maybe you or your ISP
> has to reconfig the webserver. But why not use one minivend server only
> to support two or more catalogs/shops?

The (apache)-webserver is always running on port 80 (default - not ssl).
When calling the tlink/vlink (/cgi-bin/simple e.g.) it will make a
connect to the mvend-daemon on port 7786 (default). Or in other words,
the mvend-daemon is listening to port 7786 an answers the requests. If I
have two mvend installed, they are both listening to 7786. So when I set
up two different domains, both will communicate with just one of the
mvends. In this case you can set the var TcpPort in minivend.cfg. But
changing this has no effect for me. The solution is :

untar minivend-latest.tar
grep "7786" $(find .) - note down all files with 7786 and change the
value in the new port (7787 e.g.).
install mv as usual

and it works fine :)

> Sorry for my poor english.
Willkommen im Club :)

Regards,
Marius
-
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