Skip to content

Add .epinio-sync.yaml so app watch can sync this WordPress example. #11

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

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

Add .epinio-sync.yaml so app watch can sync this WordPress example. #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions .epinio-sync.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# .epinio-sync.yaml
# app watch reads this file to decide how to sync local changes into the running pod.
#
# Run (app must already be pushed):
# epinio app watch wordpress --path .
#
# PHP/WordPress is interpreted, so this app uses files mode.
# Do not set build_cmd or binary — those fields switch watch to binary mode
# (used for compiled languages like Go or Java).
#
# On every save, watch uploads only the changed files into the pod and the
# supervisor restarts the PHP/nginx process so the new source is picked up.
#
# Push this app from the repo root (not wordpress/). Paketo needs
# BP_PHP_WEB_DIR=wordpress plus a MySQL service; those are push-time settings,
# not watch settings. See this repo's README.

# Directory inside the pod where source files are written.
# This matches the default Paketo / Cloud Native Buildpacks layout.
# The WordPress tree stays at wordpress/ under this directory.
files_dest: "/workspace/source/app"