Thank you for your advice. I had no intention of doing this myself, I have a new technical person who will be doing this, I just needed confirmation of the basic procedure.
Sent from my iPad > On 22 Feb 2017, at 20:04, Vincent Meijer <[email protected]> wrote: > > Hi Lucy, > > Personally I would have somebody on-site with you who knows that she/he's > doing before bringing anything to Production. > It is not rocket science, but you are putting your precious data online and > without the right precautions you could be at risk of losing it. > Again, this is just my opinion. :) > > However, there are some instructions available to get you started, e.g. here: > http://arches-hip.readthedocs.io/en/latest/extra/ > And especially here: > http://arches-hip.readthedocs.io/en/latest/extra/#serving-your-arches-app-with-apache > > > > Regarding getting your app to your server, there are many ways. > Often people use a code repository system like GIT, create a 'tag' (which is > a snapshot of your code) and download it from your repository to your > production server. > In your case that will only be your customized app. You should to the > installation of Arches and its dependencies like you did on the development > server. > > Regarding your database, your option 2 sounds like what you should do. > I assume your authority files and resource graphs are included in your custom > app, so after installing Arches you would do something like: > > python manage.py packages -o install > python manage.py packages -o load_concept_scheme -s > /your-app/source_data/concepts/authority_files > > > I know these directions are a little fragmentary (it's hard to explain all at > once), but I hope this helps. > > Regards, > Vincent > > >> On Tuesday, 21 February 2017 12:38:22 UTC-5, Lucy Fletcher-Jones wrote: >> Although we are a long way off from transferring to the production server, I >> would just like to ask those who are experienced in this, what the steps >> are. We are customising Arches so have many small changes. >> Do you either: >> 1. Back up the Arches programs on the test server without resource data, of >> course, and restore to the production server, assuming that the dependencies >> are the same on both. >> Or >> 2. Install Arches again on the Production server loading the modified >> authority files and resource graphs and copy over the app customisation >> directories? >> Thank you very much, >> >> Lucy >> > > -- > -- 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 a topic in the Google > Groups "Arches Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/archesproject/cqAsMqSbhRk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [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.
