ProjectEvergreen/greenwood-demo-platform-docker

does Greenwood config have to be explicitly included in container?

Open

#4 opened on Oct 29, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (0 forks)auto 404
good first issuequestion

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Just realizing now, not sure if the greenwood.config.js file needs to be included in the container explicitly, at least for when running a build?

Probably easy enough to test with something like setting the basePath and then building the container and see if it still works. If it doesn't, probably needs to be included somewhere in the Dockerfile

Contributor guide

Research direction
Test if the Greenwood config file needs to be explicitly included in the Docker container by setting a basePath and building the container.
Tech stack
javascript
Domain
devopsinfrastructure
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Docker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80