Note that there are some explanatory texts on larger screens.

plurals
  1. POsome advice needed: xampp / git / openshift
    text
    copied!<p>I've developed a PHP app with CodeIgniter, on a local xampp setup (php, mySQL, mercury) and am now trying to deploy it to an OpenShift gear.</p> <p>The local xampp app setup is ok, the openshift setup is ok, and the git setup is almost ok.</p> <p>The more I try to achieve my objective, the more complex it seems to get.</p> <p>It seems that the openshift php cartridge has a different folder structure to the xampp htdocs/application/... structure. </p> <p>So my attempts to push a git repository is pointless, until I've either done some fancy configurations to send the right files to the right folders, OR, I've scrapped xampp and switched to Apache / mySQL proper, which will then match the openshift gear.</p> <p>Am I missing something, or is there a simple solution? I'd appreciate some guidance and advice. Thanks in advance.</p> <hr> <p>My local xampp installation has htdocs with 3 applications, each inside of it's own folder, in the htdocs directory. </p> <p>The OpenShift equivalent of htdocs is php and inside is the application. For three applications, each application has it's own git repo.</p> <p>So I cannot simply change my DocumentRoot, from htdocs to php because (a) there is already a php directory - the php codebase which will then get pushed, and (b) I will be pushing all apps (in my case 3) to openshift, when I only want to push 1. </p> <p>So I'm thinking the only real "clean" way is to run my git repo interactions outside of my xampp installation entirely. </p> <p>(1) setup openshift application, (2) clone the remote repository to my local machine (inside c:\gitrepos) and then (3) copy and paste my whole app (only one app) code from htdocs to this staging area in gitrepos, and then (4) do the whole commit/push etc to deploy. </p> <p>Sounds solid enough to me, although a bit laborious....? </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload