Splendid, thanks for that Koen.  I'll let you know when I able to get that
working.

On Wed, May 6, 2015 at 9:44 AM, Van Daele, Koen <
[email protected]> wrote:

> Hi Adam,
>
> running ElasticSearch as a daemon is normally very straightforward. Just
> follow instructions like these:
> https://www.digitalocean.com/community/tutorials/how-to-install-elasticsearch-logstash-and-kibana-4-on-ubuntu-14-04
> and then you can control it with:
>
> $ sudo service elasticsearch start
> $ sudo service elasticsearch stop
> $ sudo service elasticsearch restart
>
> It will automatically run, even after a reboot of your server.
>
> Cheers,
> Koen
> ________________________________________
> Van: [email protected] [[email protected]]
> namens Adam Cox [[email protected]]
> Verzonden: woensdag 6 mei 2015 16:36
> Aan: David Lopes
> CC: [email protected]
> Onderwerp: Re: [Arches] Re: Arches 3.0 released!
>
> Hi David, I also first tried installing those as the root user.  Not sure
> if that's exactly what you mean by root privileges, or if you just mean
> with sudo, but when I did so as the root user (su root), the installation
> worked but I also had to run later commands from the root user account, and
> felt that that was not a great precedence to set.  It seemed more prudent
> to do everything as the ubuntu user, hence the addition of the sudo
> commands to the ubuntu_trusty_setup.sh script.
>
> As for setting up with Apache, here are the steps that I recorded when I
> made a successful test of that process:
>
> 1. get apache2 and the mod
>  -- $: sudo apt-get install apache2
>  -- $: sudo apt-get install libapache2-mod-wsgi
>
> 2. edit main apache2 config file
>  -- $: sudo nano /etc/apache2/apache2.conf
>
> add the top arches app directory ("crip" is the name of my app):
>
> <Directory /home/ubuntu/Projects/crip/>
>         Options Indexes FollowSymLinks
>         AllowOverride None
>         Require all granted
> </Directory>
>
> 3. edit the sites-enabled conf file:
>  -- $: sudo nano /etc/apache2/sites-enabled/000-default
>
> under <VirtualHost *:80> add:
>
> #create daemon process: make path to app and to virtualenv python
> WSGIDaemonProcess arches
> python-path=/home/ubuntu/Projects/crip:/home/ubuntu/Projects/ENV/lib/python2.7/site-packages
>
> #make group for app
> WSGIProcessGroup arches
>
> #path to app wsgi.py file
> WSGIScriptAlias / /home/ubuntu/Projects/crip/wsgi.py
>
> 4. restart apache
>  -- $: sudo service apache2 restart
>
> reference:
> https://www.digitalocean.com/community/tutorials/how-to-run-django-with-mod_wsgi-and-apache-with-a-virtualenv-python-environment-on-a-debian-vps
>
> Hope that works for you!
>
> I'm also hoping to set up elasticsearch as a daemon process so that it
> will run without having a terminal open, but have not attempted that yet.
> This is where I'm going to start with that once I'm able to get to it:
> http://wrapper.tanukisoftware.com/doc/english/launch-nix.html
>
>
>
>
> On Wed, May 6, 2015 at 3:02 AM, David Lopes <[email protected]<mailto:
> [email protected]>> wrote:
> Hi Adam,
>
> Thank you for your quick answer. I will have an in depth review it in a
> moment, although I think some of the problems I had are now solved simply
> by uninstalling with synaptic the apps mentioned in the
> ubuntu_trusty_setup.sh script and then running that same script in a
> terminal with root privileges.
>
> My main problem now, since http://localhost:8000 is running (though not
> loading all the resources of arches_hip - the command line refers them as
> truncated), is dealing with the setup of apache for production, namely with
> the wgsi.py file config. What do you have to say about that?
>
> Thank you so much, best regards.
>
> David Lopes
>
>
>
> terça-feira, 5 de Maio de 2015 às 17:33:11 UTC+1, Adam Cox escreveu:
> David, I was having the same issue for a little while.  It stemmed from
> not having postgres install correctly during the ubuntu installation (I
> also had the postgis default name set incorrectly, but I doubt that is an
> issue for you).
>
> Correctly installed postgres:
> Did you use the ubuntu_trusty_setup.sh script for setup?  I found an issue
> with that script and I'm not sure that it has been resolved yet.  There are
> two tar commands that are used to unpack the postgis installation, and they
> need to have "sudo" added to them.  Without sudo, postgis is not unpacked
> correctly (permissions issues), and so your postgres database does not have
> spatial abilities, e.g. no geometry tables.  As you see, you can see the
> database, but you'll  there are no spatial abilities.
>
> Here's a version of the ubuntu_trusty_setup.sh with those sudo commands
> added, http://www.adamcfcox.com/ubuntu_trusty_setup.sh, or you can just
> modify the script that you have downloaded.  Rerun that install script and
> see if that solves your issue.
>
> OR, if you are using AWS EC2 services, you can find the AMI that I put up
> with all of the dependencies already installed.  (If you do that, I'd like
> to know if it works for you!)
>
> As for using Apache2, I have successfully deployed with Apache2, but that
> was after solving the issue above, so hopefully it'll get working after
> that.
>
> I see your other question about the settings.py files.  No, those files
> don't have to have the same values, here's why:  There are actually three
> settings.py files in play--one in the arches package in ENV site-packages,
> one in the arches_hip package in the same directory, and then the one in
> your own app.  The settings themselves are acquired by Django in the
> reverse order that I just listed them, so a new value for a certain
> variable, say, DEFAULT_MAP_ZOOM, in your own app will automatically
> override any DEFAULT_MAP_ZOOM variable in either of the other two
> settings.py files.  Evidence of this can be found by tracing back the
> import statements at the top of each settings.py file.  Also note that any
> app can also have a "local_settings.py" file that is imported at the end of
> the settings.py file, so that is an additional way to override certain
> variables.
>
> Hopefully Alexei can correct me if any of that information is incorrect...
>
> Good luck!
>
> On Thursday, April 23, 2015 at 11:59:46 AM UTC-5, Alexei Peters wrote:
> Hi Everyone!
>
> Today we're happy to announce the release of Arches 3.0 and HIP 1.0 !
>
> Arches 3.0
> The documentation can be found here
> https://arches3.readthedocs.org/en/latest/
>
> Arches 3.0 is a brand new system which includes:
>
>     *   A new and updated mobile friendly UI.
>     *   A Reference Data Manager (RDM), a core Arches module which enables
> the creation and maintenance of controlled vocabularies for use in
> dropdowns and controlled fields within the various Arches Resource forms.
> It also includes import and export to the SKOS format.
>     *   Built in support for forms and report templates
>     *   An integrated Elastic search engine
>     *   A fully localizable UI
>     *   much more...
>
> Arches 3.0 is available on Pypi at https://pypi.python.org/pypi/arches
> for those wishing to pip install the software and the code is always
> available on Bitbucket at https://bitbucket.org/arches/arches3
>
> If you want to test the Arches system right away with a proven application
> see below about installing the HIP.
>
>
> HIP (Heritage Inventory Package) 1.0
> The documentation for the HIP can be found here
> http://arches-hip.readthedocs.org/en/latest/
>
> The HIP is an application that sits on top of Arches 3.0 and extends
> Arches capabilities with predefined resource graphs, forms, and report
> templates.  The HIP was used as the basis for the successful
> HistoricPlacesLA.org<http://historicplacesla.org/> site.
>
> HIP  1.0 is also now available for download at
> https://pypi.python.org/pypi/arches_hip or on Bitbucket at
> https://bitbucket.org/arches/hip
>
>
> As always, please visit the archesproject.org<http://archesproject.org>
> site for more information.
>
> Cheers,
> The Archesproject team!
>
> --
> -- To post, send email to [email protected]<mailto:
> [email protected]>. To unsubscribe, send email to
> [email protected]<mailto:
> archesproject%[email protected]>. For more information,
> visit https://groups.google.com/d/forum/archesproject?hl=en
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Arches Project" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/archesproject/qW9nwnOzLyY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected]<mailto:
> [email protected]>.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> -- To post, send email to [email protected]. To unsubscribe,
> send email to [email protected]. For more
> information, visit https://groups.google.com/d/forum/archesproject?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Arches Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected]<mailto:
> [email protected]>.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to