[INFRA-70] Provide PFS http server for conda repository Created: 21/Oct/16  Updated: 13/Oct/17  Resolved: 13/Oct/17

Status: Won't Fix
Project: Software Development Infrastructure
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: cloomis Assignee: shimono
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Could we get a PFS development web server? The immediate use-case is for a conda channel for patches/additions to the LSST conda installation. But one can imagine others (documentation, ICS conda channel).

For conda, http or https, and only serving static files. rsync'ing files in might be sufficient write access.



 Comments   
Comment by shimono [ 17/Nov/16 ]

Pages at https://pfspipe.ipmu.jp is managed under git (at github, no auto deploy).
We can have any directory specific to this purpose, managed under git.

Comment by cloomis [ 17/Nov/16 ]

OK,

  1. How do the actual ``pfspipe`` pages get updated after the github repo gets changed?
  2. Where in the pfs_www repo would a static and hidden directory containing a tree of files of various types and names go?

For conda there will be big .tgz files, etc.

Comment by shimono [ 17/Nov/16 ]

1. periodic update and/or one-time hand operation by sysadmin
2. pfs_www is for pfs.ipmu.jp, which is under simple CMS. it's not easy to handle various types

> For conda there will be big .tgz files, etc.
I was afraid so, actually.
Then, it should be better to have some space via putting files, or to build conda repository at server.
Easiest way in server operation point of view, is to provide one WebDAV URI (on pfs.ipmu.jp or pfspipe), which is in public at some point on pfspipe. e.g.:
webdav: https://pfs.ipmu.jp/webdav-pfspipe/
public point: https://pfspipe.ipmu.jp/conda/

If you are thinking to have non-autogen-ed documents, I'd suggest to host in pfs_www_pipe repo. If you are thinking to have autogen-ed documents like via sphinx, ask to build dedicated processing environment on server or consider to follow other documents (like readthedocs).

Comment by cloomis [ 18/Nov/16 ]

webdav would work, I think. Though rsync would easier. Access does need to be pretty general: allow deleting things, etc. Definitely non-autogen-ed. Sorry....

If you have ipv6, http://odie.toestub.org:8088 has a sample tree with just one product in it. That's what I'd like to be able to actively maintain. (Sorry, that host is all I have complete access to right now). conda search --override-channels -c http://odie.toestub.org:8088/stack is how it would appear to most.

Comment by shimono [ 18/Nov/16 ]

ok.

site: https://pfspipe.ipmu.jp/conda/
webdav: https://pfs.ipmu.jp/webdav-conda/ (login required)
rsync: ssh to pfs.ipmu.jp:/server/services/conda/

if you could configure, please close this.

Comment by cloomis [ 13/Oct/17 ]

Thanks for all the work. In the end we will not use conda distributions.

Comment by shimono [ 13/Oct/17 ]

Since,
> Thanks for all the work. In the end we will not use conda distributions.
changed resolution to WONTFIX, and filed INFRA-162.

Generated at Sat Feb 10 16:49:06 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.