Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds Dockerization instructions to README. #19

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Lugghawk
Copy link

Adds README instructions for dockerizing the play-react app.

I contained the information all within the Readme, since the modifications are generally only something you want if you're going to be running your app in a container. Not sure if you'd prefer another method of adding these instructions. I just went through this process so I thought I'd capture it by adding it somewhere. The section added to the README is relatively substantial, so if there's a more appropriate way to share this information, let me know (scala-play-react-docker-seed?)

@yohangz
Copy link
Contributor

yohangz commented Nov 18, 2019

@Lugghawk great contribution. It's better if you can move this to another md file and link it to the primary (readme.md). Also, the same should be reflected in other related seed projects.

scala-play-angular-seed
java-play-react-seed
java-play-angular-seed

@ptrdom
Copy link
Member

ptrdom commented Apr 13, 2022

@Lugghawk Quite a while has passed since your PR, since we moved the repository under Play Framework organization we are trying to get it updated. I would think that the Docker setup is important enough that we should not only just have docs for it, but have it included in the main build. Would you like to work on that?

@Lugghawk
Copy link
Author

@ptrdom I'm not sure what's involved, but with a bit of guidance I could give it a shot.

What does it mean to be "included in the main build"?
Should this doc PR be retargeted somewhere else?

@ptrdom
Copy link
Member

ptrdom commented Apr 13, 2022

What does it mean to be "included in the main build"?

Oh, I meant just that we could actually implement the changes that you documented, instead of only documenting what is required to be implemented and leaving the implementation up to the user of this seed project. What do you think about that?

Should this doc PR be retargeted somewhere else?

This is the main repo now, as you can see it is under playframework organization already.

@Lugghawk
Copy link
Author

instead of only documenting what is required to be implemented and leaving the implementation up to the user of this seed project.

Ah! So you'd like it to be the new default. That sounds fine to me, I can try and work on those changes over the next few days. Shall I append it to this same PR (with a more appropriate title/etc) or should I close and start a new one?

@ptrdom
Copy link
Member

ptrdom commented Apr 13, 2022

Great to hear! I think you can just continue your contribution on this PR.

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.

None yet

3 participants