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".

Thanks,
Branden



On Tue, Jul 16, 2013 at 6:38 AM, Samuel Gutiérrez Jiménez-Peña <
samuelgutierrezjime...@gmail.com> wrote:

> Hi,
>
> thanks  to Nicolaas for the pull request  and Branden for the help offered
> to me with the problem to install it.
>
> I've managed to install on a server OAE, although it took me a few time
> with your help I got it at last.
>
> Although I have a doubt regarding the etc/hosts file because I've put, on
> my computer,  the domain for access to OAE, but also I have another website
> set to appear in the same domain.
>
> How could I do to make OAE continue appearing on the server but on a
> subdomain for both pages were available without overlapping?
>
> Regards, Samuel.
>
> El 15/07/2013, a las 13:54, Nicolaas Matthijs <
> nicolaas.matth...@caret.cam.ac.uk> escribió:
>
> I have just submitted a Pull Request [1] that updates the documentation:
>
>    - Replace <%= nginxConf.NGINX_USER %> and <%= nginxConf.NGINX_GROUP
>    %> with the OS user and group that the nginx process should run as
>    - Replace <%= nginxConf.NGINX_HOSTNAME %> with the same value you
>    configured for the global administration server host in /etc/hosts (the
>    one whose current value would be "admin.oae.com"). Note:The server_name 
> property
>    for the user tenant server further down the configuration file
>    should remain set to "*".
>    - Replace all instances of <%= nginxConf.UX_HOME %> with the full
>    absolute path to your cloned 3akai-ux directory (e.g.,
>    /Users/branden/oae/3akai-ux) or the 3akai-ux production build directory
>    (e.g., /Users/branden/oae/3akai-ux/target/optimized)
>    - Replace <%= nginxConf.LOCAL_FILE_STORAGE_DIRECTORY %> with the full
>    absolute path that you configured for file storage in the Hilary
>    config.js step
>
> [1] https://github.com/oaeproject/Hilary/pull/598
>
> Hope that helps,
> Nicolaas
>
>
> On 12 Jul 2013, at 13:09, Branden Visser wrote:
>
> Hi Samuel,
>
> On Fri, Jul 12, 2013 at 5:59 AM, Samuel Gutiérrez Jiménez-Peña <
> samuelgutierrezjime...@gmail.com> wrote:
>
>> Hi everyone,
>>
>> This file doesn´t contains labels, such as: <% = NGINX_USER%>, <% =
>> NGINX_GROUP%> ... I suppose that this file should be replaced by:
>> https://github.com/oaeproject/3akai-ux/blob/master/nginx/nginx.conf
>>
>> It is right? If so, the tags: <% = nginxConf.NGINX_USER%> would be the
>> same label as <% = NGINX_USER%>, or take another path setting?
>>
>>
> Yes you should replace the default file with the one in 3akai-ux, and
> replace all of the <%= ... %> labels. You are correct, the README.md
> incorrectly says <%= NGINX_USER %> when it should actually say <%=
> nginxConf.NGINX_USER %> and so on. I will change this.
>
> Remember these labels are not variables that Nginx can use, you will
> actually have to replace them with the actual values. For example, search
> and replace all instances of:
>
> <%= nginxConf.NGINX_USER %> with the actual OS user you want Nginx to run
> as (e.g, for my development laptop I replace it with "branden").
>
> Hope that helps,
> Branden
>
>
>> Regards, Samuel.
>> _______________________________________________
>> oae-dev mailing list
>> oae-dev@collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>>
>>
> _______________________________________________
> oae-dev mailing list
> oae-dev@collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>
>
>
>
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to