airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRAVATA-2581) Manually deploy Django version of dev seagrid
Date Thu, 01 Feb 2018 20:17:00 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347591#comment-16347591
] 

Marcus Christie edited comment on AIRAVATA-2581 at 2/1/18 8:16 PM:
-------------------------------------------------------------------

Updating the dev django deployment:
 * git pull
 * source ../venv/bin/activate
 * pip install -r requirements.txt
 * Update settings_local.py for any newly added properties
 * {{find . -name node_modules -prune -exec rm -rf {} \;}}
 ** this removes the built node modules and including the private modules for the common and
API shared JS code so that they are forced to rebuild. The NPM way would be to increment version
numbers each deploy. I'm not sure what's the best way to manage this at this time.
 * ./build_js.sh
 * python manage.py collectstatic


was (Author: marcuschristie):
Updating the dev django deployment:
 * git pull
 * source ../venv/bin/activate
 * pip install -r requirements.txt
 * Update settings_local.py for any newly added properties
 * ./build_js.sh
 * python manage.py collectstatic

> Manually deploy Django version of dev seagrid
> ---------------------------------------------
>
>                 Key: AIRAVATA-2581
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2581
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message