Skip to content

Remove deprecated configuration files and scripts from quickstart and quickstart-pcs directory - #149

Open
alexlovelltroy wants to merge 1 commit into
mainfrom
chore/deprecate-docker-compose
Open

Remove deprecated configuration files and scripts from quickstart and quickstart-pcs directory#149
alexlovelltroy wants to merge 1 commit into
mainfrom
chore/deprecate-docker-compose

Conversation

@alexlovelltroy

Copy link
Copy Markdown
Member

Description

New users were getting confused by the many ways to set up and test OpenCHAMI. This PR deprecates two docker-compose environments that were no longer getting updates.

Fixes #(issue)

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

For more info, see Contributing Guidelines.

… quickstart-pcs directory

Signed-off-by: Alex Lovell-Troy <alovelltroy@lanl.gov>
@synackd

synackd commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

I noticed in OpenCHAMI/openchami.org#102 that it mentions the quickstart/docker-compose as legacy, seemingly to imply that it is still available (archived), but not supported officially. Did we want to do some sort of archiving instead of deletion to support that?

@davidallendj

Copy link
Copy Markdown
Contributor

I noticed in OpenCHAMI/openchami.org#102 that it mentions the quickstart/docker-compose as legacy, seemingly to imply that it is still available (archived), but not supported officially. Did we want to do some sort of archiving instead of deletion to support that?

To add to this, I thought we had a discussion before about keeping this around in case someone else wanted to reference this for a docker-compose deployment or adopt/maintain it themselves in the future?

@alexlovelltroy

Copy link
Copy Markdown
Member Author

I noticed in OpenCHAMI/openchami.org#102 that it mentions the quickstart/docker-compose as legacy, seemingly to imply that it is still available (archived), but not supported officially. Did we want to do some sort of archiving instead of deletion to support that?

I thought all reference that remained included a specific branch/commit which remains. Given that these are no longer supported, I'd rather delete them to avoid people accidentally using them.

I'll also review the website and see if there are any more edits needed to remove references.

@synackd

synackd commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

I think accessibility through version control history is probably sufficient for deletion as long as the website docs match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants