Sharing a directory in RAM
I have a use case....A team develops automation scripts for a variety of teams. The code is developed and stored in RTC which they make available to the broader community of users. The package they make available is a folder structure nested about five levels deep with around 150 files. It is too big to zip up. We would like to put this into RAM. The ideal situation would be to link back to the folder in RTC but URL would take you to the folder in the web client and in the webclient you can only download one file at a time. They don't want to train all their users to the on the eclipse client. So is there a way to upload the root directory into a RAM asset?
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Why is it too big to zip up? RAM stores everything zipped up anyway. It uses the modern zip technology that allows zipping up billions of files ( :-) ) to many GB file sizes.
150 files is not very many to zip up.
As Rich noted, if you store the directory structure in RAM (which RAM will zip anyways), you could browser the directory structure, as well as download all (zipeed), or access artifacts directly.
Beyond that you can use the governance/versions of RAM... and (OSLC) link it to workitems in RTC.