Open Ross-ROE opened 3 months ago
18/JUL/24 @astrodb reported via email
To progress following issues #558 & #559 we'll either need sudo access, or Mark will need to install for us the Postgres and Python3 software via the OS. See those issues for details.
Also, someone with root access needs to setup the common file system: Maybe the top-level should be the name of the archive? e.g.
/moons-archive/database/ /moons-archive/products/
These will need read-write access for all.
Thanks for the database directory. Can we have the products directory too? Not sure we'll need anything else from the shared file system.
On another point, how can I comment on this project with my other account - do we want this project to be writable by anyone??
@Ross-ROE - tell me name of your other account and I can add it to the repo
That's the thing - I seem to be able to comment here with my other account, which I'm surprised about (see comment prior to my previous one). Is the repo at least protected to just WFAU staff? As I was intending to use it for the new code.
@Ross-ROE - it was setup as a public repo, visible to anyone. Currently the 14 members of the WFAU organisation have write access.
OK, that's fine - was just surprised anyone can comment here! Only problem then is I'm now getting twice the email notifications! That'll teach me not to check which account I'm using!
We'll be using the VM to host both the curation database and run the curation scripts, unlike old generation system.
We'll need to define a file system layout to store databases, flat files, which doesn't have to follow the old system as we'll be using all new software.
Access to the VM should be granted for all science archive staff via individual user accounts.
We'll need to define a way of listing and managing the standard tools we want to have available on the VM too, like "git", "screen", "nano", "rsync".