Forum OpenACS Development: Re: Unusable Development server... Solutions?

Collapse
Posted by Torben Brosten on
Are you sure you are wanting to have a development server as a subsite of a production server?

A subsite of a production server is still part of a production server, sharing the same db, procs etc. Something breaks in the subsite, it breaks for the production system.

Are you wanting a separate development server on the same ip as the production server?

There are many ways to handle this.

The simplest configuration shares the same domain name, just use a different port, and assign different "subdomain.domains" to both, so there is no confusion with cookies, for example: mysite.com:80 for production and www.mysite.com:8000 for development.

One can also use a reverse proxy to serve multiple domains from the same ip, with each domain serving a separate openacs instance.

Collapse
Posted by Malte Sussdorff on
Bob was not talking about taking a subsite on the production server. The idea is to take the production site dump file, copy it over to the developement server (different computer), install it, reset all host nodes, reset all parameters (notably SystemURL and CookieDomain) and reset every other instance of mysite.com on mysite.ws.

What we found though is that the new server does not set the cookie at all. I tried to set a cookie manually using the ad_set_cookie procedure, to no avail.

Note, this behaviour does not show up at (at least to my experience now coming to think of it), if you are using a different subdomain specific for development. This might be worth a try, to say:

develop.mysite.com is redirected via DNS to the development server's IP address and we make sure that develop.mysite.com cannot be a subdomain for mysite.com (on the production server).