revisit shared dev LIMS for Pika

[danielsf]

Since Pika is still required to touch ruby strategies and run datafixes on the LIMS database tables, we should revisit the conversation around #404 so that Pika is able to test changes to LIMS strategies and datafixes.

Tasks

• Have meeting with Nick Mei and Jake Samson (before Jake leaves) about what is involved in standing up a new, shared, dev LIMS instance (for reference: Sergey built a dev LIMS instance 2 years ago and was able to resume using it in 2022 after just running the rake command to update the database)

Optional

• Possibly reach out to the LIMS team to see if there is another way for this team to validate/test changes to LIMS. As Adam points out: no one on Pika is a ruby developer; we will be operating in a dangerous space every time we touch the ruby strategies.

The outcome of this meeting needs to be a choice between

• Having one shared dev LIMS instance for all of Pika
• Each member of Pika being able to and responsible for standing up their own dev LIMS as needed
• The decision to start negotiations with the LIMS team about who really owns changes to the ruby strategies

[aimichaelwang]

Low priority for now. Can set up on WorkStation following Nick Mei's tutorial. Most likely 1 day work for each member.