Limesurvey Openshift不需要重新安装时混帐推新文件

Question

的问题是在Openshift修改文件，同时利用从下面的混帐

https://github.com/gshipley/limesurvey-quickstart 

Limesurvey安装完成后，我在我的本地回购添加新文件例如php/front-end.html，git push它，然后在openshift访问我的limesurvey应用程序，它再次把我带到安装程序页面。

为什么它每次都影响和重新设置石灰调查安装我git push？我该如何解决它？

注：我不修改任何limesurvey文件只是增加一个新的。

下面是git的日志：

>git status 
# On branch master 
# Changes not staged for commit: 
# (use "git add <file>..." to update what will be committed) 
# (use "git checkout -- <file>..." to discard changes in working directory) 
# 
#  modified: php/front-end.html 
# 
no changes added to commit (use "git add" and/or "git commit -a") 

>git add php/front-end.html 

>git commit -m "Test Front End" 
[master dd7f21d] Test Front End 
1 file changed, 1 insertion(+) 

>git status 
# On branch master 
# Your branch is ahead of 'origin/master' by 1 commit. 
# (use "git push" to publish your local commits) 
# 
nothing to commit, working directory clean 

>git push 
Counting objects: 7, done. 
Delta compression using up to 4 threads. 
Compressing objects: 100% (4/4), done. 
Writing objects: 100% (4/4), 362 bytes, done. 
Total 4 (delta 3), reused 0 (delta 0) 
remote: Not stopping cartridge mysql because hot deploy is enabled 
remote: Not stopping cartridge php because hot deploy is enabled 
remote: Not stopping cartridge phpmyadmin because hot deploy is enabled 
remote: Building git ref 'master', commit dd7f21d 
remote: Checking .openshift/pear.txt for PEAR dependency.. 
remote: Preparing build for deployment 
remote: Deployment id is dc93388e 
remote: Activating deployment 
remote: Not starting cartridge mysql because hot deploy is enabled 
remote: Not starting cartridge phpmyadmin because hot deploy is enabled 
remote: Not starting cartridge php because hot deploy is enabled 
remote: ------------------------- 
remote: Git Post-Receive Result: success 
remote: Activation status: success 
remote: Deployment completed with status: success 
To ssh://<long guid>@appname-namespace.rhcloud.com/~/git/appname.g 
it/ 
    91e3033..dd7f21d HEAD -> master 

Answer 1

你基本上是在写作的时候，你做一个混帐推那些在安装过程中产生的任何配置文件。
我可以看到两种方法来解决此问题：
1.）将安装过程中创建的文件复制到OPENSHIFT_DATA_DIR（〜/ app-root/data）中，然后在您的deploy动作钩子中为它们创建符号链接。 2.）在openshift上安装，然后ssh到你的设备，并将创建的文件复制回你的本地git工作目录，并使用git将它们添加到你的版本库中。& & git commit，那么当你将git推到你的装备时，这些文件将被部署。