Hello Rob, Yes I did all that following the PDF manual (or thought I had). On rereading the documentation I missed the bit that said "navigate to folder where you’ve cloned arches" So my Vagrant instance couldn't see the arches folder (I didn't appreciate the importance of where you run 'vagrant up' from)
In which case I'd suggest making this explicit in the doc by putting cd ~/projects/arches vagrant up I'll try again. By the way I'm not a 'hard core' developer but I hope to be able to contribute. I think the Vagrant part is important for users of other Linuxes. I agree not for production but for evaluation. Another issue is that Red Hat / Centos servers are the most used in production. I'm already renting a Centos server that I run my as my production server and I'm not too keen having to move everything to Ubuntu hosting or run two servers, but that's an issue for another day. Thanks Andy On Thursday, May 22, 2014 11:06:17 PM UTC+1, Rob Gaston wrote: > > Hi Andy, > > if you followed the latest documentation you should have cloned the > repository as the first step, which would have gotten you the latest > version of the setup script. From the docs: > > Step 1: Clone Arches >> >> Start by getting a copy of the Arches code using a local Mercurial >> client: >> >> 1 hgclonehttps://bitbucket.org/arches/arches~/projects/arches >> Then, (assuming you want to develop using the CDS package) clone the CDS >> repo into your packages folder: >> >> 1 hgclonehttps:// >> bitbucket.org/arches/cds~/projects/arches/archesproject/packages/cds >> >> And create a settings local file as described in “Loading the CDS >> Package”, if you’re using linux, you can run the following commands: >> > touch ∼/projects/arches/settings_local.py >> > echo “INSTALLED_PACKAGES = (‘cds’,)” >> ∼ >> /projects/arches/settings_local.py >> > Did you do this first? Then you must cd into the arches directory before > running "vagrant up". From the sound of your ticket, I don't think these > steps were executed as advised in the latest documentation (perhaps you are > looking at some old version of the docs?). > > As you've already run "vagrant up" before, you may need to first run > "vagrant destroy" to get a fresh VM. > > Cheers, > - Rob > > > On Thursday, May 22, 2014 2:50:46 PM UTC-7, [email protected] wrote: >> >> Hello, I've just hit the same Vagrant issue - but I'd not seen this >> thread first unfortunately. >> I'm trying the corrected vagrant_setup.sh script now - compiling as we >> speak... >> >> I'm on OpenSuse 13.1 Linux - it's clear would be a major task to get >> Arches to install on this. I made a quick list of dependencies which I >> don't have: >> >> build-essential ??? >> postgresql-9.2 YES 9.2-4.12 postgresql92 >> postgresql-server-dev-9.2 ? YES postgresql-devel >> libxml2-dev YES libxml2-devel >> libproj-dev YES libproj-devel >> libjson0-dev ??? NO only libjson0 >> xsltproc NO ??? Have libxslt-tools libxslt-devel >> docbook-xsl ??? docbook-xsl-stylesheets >> docbook-mathml ??? various other docbook >> libgdal1-dev NO have libgdal1 >> postgresql-contrib-9.2 NO >> postgresql-server-dev-9.2 NO >> libpq-dev NO libpgqxx-4_0 libpgqxx-devel >> >> So I decided to use Vagrant, which I've not used before. I already had a >> VirtualBox install so that was good. >> I've posted my suggestions following my experience following the Vagrant >> install instructions as a new issue: >> >> https://bitbucket.org/arches/arches/issue/375/installation-manual-suggestions-for >> >> Thanks >> Andy >> > -- -- 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.
