Hi Branden, I would have to look well the configuration of DNS to do it properly, If I have any questions about that I would ask you by mail.
With respect to the server's home page is the index.php created in var/www/ when I go to http://87.106.207.149, open that file. Also when I start OAE in that configuration server runs in the same direction, getting display a blank page instead of index.php OAE. What files and what settings should be to not to overlap? Regards, Samuel. El 17/07/2013, a las 19:36, Branden Visser <mrvis...@gmail.com> escribió: > Hi Samuel, > > To deploy for an environment that users can access from their computers, > there will need to be an entry in a DNS server (either an authoritative DNS > host such as Dyn.com so all users on the internet can access it, or a DNS > server hosted within your intranet if you just want users within your > organization to use it). > > When you say there is a conflict, do you mean that there are other > applications installed on the same machine that are picking up the default > web ports? What is the "server homepage", is that hosted on the same machine > you installed OAE on? > > Thanks, > Branden > > > > On Wed, Jul 17, 2013 at 12:28 PM, Samuel Gutiérrez Jiménez-Peña > <samuelgutierrezjime...@gmail.com> wrote: > Hi Branden, > > I understand that changing the etc/hosts file on my computer can access the > development environment and also to not overlap both directions, also putting > 127.0.0.1 (localhost) in etc/hosts. > > At this point, my intention is to implement a production environment on a > server, but I can't understanding very well the steps. The installation was > performed correctly with your help, but now I need the configuration to avoid > overlaps these addresses. I attach the etc/hosts file from server, where you > can see the configuration that I've made: > > > > I think that the cause of the overlap is that 87.106.207.149 address is > redirected to the server home page, so OAE overlaps this page. I don't know > what would be the configuration for any user could enter in OAE without touch > the etc/host, to be a production environment. > > If you needed any more file to understand a little more the server, ask me. > > Regards, Samuel. > > El 17/07/2013, a las 16:43, Branden Visser <mrvis...@gmail.com> escribió: > >> Hi Samuel, >> >> I think this goes without saying but I want to make sure it's clear, that >> updating your /etc/hosts file is only sufficient for a local development >> environment / local trial. If you want to set up the system on a server that >> other users can use, you'll need to actually make a DNS entry for the server. >> >> That said, if you want to set up an /etc/hosts entry on a subdomain of a >> remote server (that only you can resolve), that is possible without >> conflicting with a remote server, so long as it is a subdomain. For example: >> >> Say you have a remote server set up at www.example.com, which resolves to IP >> 123.45.67.89. You can set up your local development environment with an >> /etc/hosts entry like this: >> >> 127.0.0.1 oae.example.com admin.example.com >> >> And those will not conflict with "example.com", or "www.example.com". >> > > >
_______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
