OpenShift Web server refreshes site back to original content about s2i-php-container HOT 5 CLOSED

for (1) git repo content gets added to the image as the image is built, so that will always be present.

for (2) it's not clear to me how you're introducing the changes, but if you are making changes to the running container then yes, those changes will be lost if either the container is restarted, or you build a new image.

If that's not what you're doing, i think we'll need more exact recreate steps. @luciddreamz or @coreydaley, either of you have experience w/ drupal that might help here?

from s2i-php-container.

It's potentially the same issues that we had on V2. You need to pick which way you want to make your changes:

• Run the drupal setup on OpenShift and then make all of your modifications through the Drupal admin.
• Do your setup locally and then commit your changed files to the repo so they don't get wiped out.

This issue also affects WordPress users.

from s2i-php-container.

Thanks @bparees and @coreydaley for your quick response. I really appreciate it.

Now, I get to understand how the server works. Since there's no way for me to execute Drush command(which I think would be first best step to configure and work on Drupal site), and that Drupal installation generates incomplete files and folders on the server that leads me to broken pages and URLs,

• Does Drupal admin changes are saved on the image even if build is restarted?
• Will my local changes commits on repo automatically reflects on the server or does it applied after another build?

I'm still new to this set up and I would really appreciate your help. I can't find Drupal related issues on google as I'm getting the openshift.redhat articles.

Thanks!

from s2i-php-container.

Does Drupal admin changes are saved on the image even if build is restarted?

are you sure you mean "build is restarted" here? if the pod/container is restarted then no, any changes you made via the admin interface will not be saved, unless you've configured the image to save its state to a volume and mounted an appropriate persistent volume into the pod.

Will my local changes commits on repo automatically reflects on the server or does it applied after another build?

applied after another build.

Here's the flow:

1. you put some content in a git repo
2. you run a build which takes the git content and adds it to an image you specifiy, producing a new application image
3. that image gets run as a container. Any changes you make inside the running container will be lost if the container restarts, because it will start from the application image again, which is not changed.
4. if you want to change the image, you go to (1) (update content in a git repo)

that's the basic flow.

Again, you can also store content on a volume in which case the content can be preserved through restarts and you can edit it while the pod is running and not lose the changes, but the basic php image isn't designed to do this today, so the best thing for you to do is make your changes in your git repo, not in the running container.

from s2i-php-container.

@johnreytanquinco Do you have any further questions/comments or should we go ahead and close this issue?

from s2i-php-container.