Add notes on how to install addon packages in an extended container.

[Rudd-O]

No description provided.

[stevepiercy]

A required minor syntax fix, and an optional suggestion.

[Rudd-O]

Fixed. Please merge at your leisure. Thanks.

[Rudd-O]

All addressed.

[Rudd-O]

@stevepiercy tests aren't running.

[stevepiercy]

Syntax fixes.

[stevepiercy]

@stevepiercy tests aren't running.

Yeah, looks like someone with the GitHub username/password is required, or at least someone more familiar than I with how to successfully run this step in the GitHub Action.

https://github.com/plone/plone-backend/actions/runs/3170285071/jobs/5162771257

[davisagli]

@Rudd-O Can you submit a PR from a branch within the plone/plone-backend repository, instead of from your fork? Then the tests should be able to run.

From your perspective, this would mean adding [email protected]:plone/plone-backend.git as a git remote, pushing the branch there, and then opening a PR from that branch. You should have access to do this if you've already signed the Plone contributer agreement.

[stevepiercy]

Oh, I had a problem recently in PyCharm pushing to one or two Plone repos recently. I had to purge all GitHub entries in my macOS Keychain, reauthorize, and then I was able to push.

[Rudd-O]

Do we need to run the tests to commit this? This is turning into a lot of work just to update a README.

[ericof]

imo, all documentation should go to plone/documentation

[stevepiercy]

imo, all documentation should go to plone/documentation

I agree. I looked at this entire README for the first time just now. It does not make sense to maintain duplicate information in two places, the other being at https://6.dev-docs.plone.org/install/containers/index.html and its related files. Sorry for not noticing sooner.

On the plus side, contributing to Plone 6 Documentation is much easier.

Unless there is a very good reason not to do the following, let's move any content from this README into Plone 6 docs, and replace it with a link to them. The only thing that might be a concern is Plone 5 support and getting that into the Plone 5 docs, which is not simple or easy.

What do y'all think 🤔 ?

[ericof]

README here should have only information about the latest versions (and this is taken care on the 5.2.x branch).
So, let's make documentation the default place

[stevepiercy]

I created #80 so we don't forget, and to track it in the Plone 6 Docs release GitHub project.