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.

Sign up for GitHub

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

Jump to bottom

Move deployment assets to deploy directory #175

Closed
marein opened this issue Apr 7, 2023 · 0 comments · Fixed by #176
Closed

Move deployment assets to deploy directory #175

marein opened this issue Apr 7, 2023 · 0 comments · Fixed by #176
Assignees
@marein
Labels
priority:low type:infrastructure type:maintenance

Comments

@marein
Copy link
Owner

marein commented Apr 7, 2023 •
edited
Loading

As more deployment assets will be added, see #170, they should be grouped in a /deploy directory. #170 already does this. This issue only affects /docker-compose.production.yml which may be moved to /deploy/play-with-docker/docker-compose.yml.
@marein marein self-assigned this Apr 8, 2023
@marein marein linked a pull request Apr 8, 2023 that will close this issue
Move deployment assets to deploy directory #176
Merged
marein added a commit that referenced this issue Apr 14, 2023
@marein
Move deployment assets to deploy directory (#176)
9ad7d2e 
Move Play with Docker file #175.
The name of this deployment is single-server because
it serves multiple purposes. It's used as an example for
deploying production images through Docker Compose
and it will be passed to Play with Docker.

Deployment assets are grouped as more will follow,
e.g. with #118.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marein marein

Labels
priority:low type:infrastructure type:maintenance
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move deployment assets to deploy directory marein/php-gaming-website
1 participant
@marein