[
https://issues.apache.org/jira/browse/AIRAVATA-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961222#comment-16961222
]
Marcus Christie commented on AIRAVATA-3019:
-------------------------------------------
For deployment I'm planning on pushing the built jars to the
django-seagrid/static/seagrid-rich-client directory. Also plan to add an alias
in the virtual host config of /seagrid-rich-client ->
/static/seagrid-rich-client. This will allow the current update URL
(https://seagrid.org/seagrid-rich-client/) to keep working.
I've run into an issue building a Mac DMG installer, but since the update url
isn't changing, we don't technically need new installers.
> SEAGrid Desktop Client changes
> ------------------------------
>
> Key: AIRAVATA-3019
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3019
> Project: Airavata
> Issue Type: Task
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
> Fix For: 0.19
>
>
> Update the SEAGrid Desktop Client to accommodate group based auth changes.
> h5. TODO
> - [x] specify group resource profile id in config
> -- similar to AIRAVATA-3085
> - -[ ] check group membership instead of roles-
> -- not relevant, SEAGrid DC assumes user has privileges
> - [x] get last status in array for most recent one
> -- verified this is needed
> -- similar to AIRAVATA-3089
> - [x] setup sftp server in staging environment so that it can be tested
> - [x] figure out how to integrate SEAGrid desktop builds with download links
> in Wagtail CMS
> - [ ] how much work to query for accessible app module, group resource
> profile, accessible app deployments, etc.?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
