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 site for more information.
>
> Cheers,
> The Archesproject team!
>

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