[FOLIO-3550] Spike - investigate use of platform-minimal to facilitate development environments Created: 05/Aug/22  Updated: 22/Aug/22

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Craig McNally Assignee: Steve Ellis
Resolution: Unresolved Votes: 0
Labels: back-end, platform-minimal
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-3548 Verify and fix platform-minimal Closed
Sprint:
Development Team: Volaris
RCA Group: TBD

 Description   

Overview

It's no secret that getting a full fledged, functional deployment of OKAPI running locally on a developer's system can be challenging. The vagrant boxes for instance have hardware requirements that are often well beyond what developers have access to. While shared rancher/scatch environments help, having the ability to standup a bare-bones system locally, then adding in a few modules under development would be helpful.

FOLIO-3548 Closed verifies and fixes the platform-minimal definition, and FOLIO-3549 Open creates automation to perform routine builds of that platform, but for this to be useful to developers, we probably need to generate some additional artifacts, e.g. docker compose files, ansible scripts, vagrant box, etc.

The goal of this spike is to determine what makes the most sense here, document the findings/ideas, and create user stories to more this forward.

It may even be the case where platform-minimal isn't sufficient, and to really be useful to developers we need something that builds upon platform minimal, adding a few more modules and/or additional infrastructure (kafka/elasticsearch/etc.)


Generated at Thu Feb 08 23:28:57 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.