What ways are there to work on a project in a testing environment where the Git commit needs to be different to the PHP code used for testing and dev? -

What ways are there to work on a project in a testing environment where the Git commit needs to be different to the PHP code used for testing and dev? -

in project deployable version needs have re-create of each of external libs, different config file , install , setup files, security concerns, main project set reject run if present. upstream copies of other projects need committed repo. how can work on code running on localhost file layout , file contents dev , testing different need commit?

background

i working on project on hosted on github , main ide netbeans has imperfect git back upwards (good plenty >99% of needs). project in php , uses several other projects libraries.

as netbeans not have best back upwards sub-repos have chosen maintain each additional project in separate project. fine central project looks @ config info find these outside libs.

half answer

my instinct suppose there need "build stage" prior committing github repo how on earth go setting up?

i write sort of homebrew thing when pull other people's contributions need reverse process unless had branch builds , branch working copies seems needlessly complex , leave dev(s) config info on public display (not mention updates beingness mess).

i have seen others have wrestled similar problems no conclusion (at time of asking) (how force , pull github without sharing sensitive information? smudge & clean?) looking might help me come solution

my main ide netbeans has imperfect git support

most devs utilize command line. switch netbeans conflict resolver occasionally, good, normal stuff console faster.

my instinct suppose there need "build stage" prior committing github repo

... unless had branch builds , branch working copies

no, there ever 1 repository. improve think of repo code history, rather deployment state. branches should features or big changes, merge mainline/master.

there deal of options available when deploying. first composer, mark points out: when deploying issue install or update command, fetches dependencies satisfy library requirements recursively. can utilize bower same thing javascript dependencies.

some deployment strategies prefer build locally , scp/rsync remote server. composer , bower still idea, write build script (using ant or phing, example) create build re-create in local temporary folder, , send server. mutual here force new release folder on server, , swap symlink or apache config file when it's ready go live.

the deployable version needs have re-create of each of external libs, different config file , install , setup files, security concerns

assuming web project, have tried adding sensitive environment info apache configuration file? can trivially read in php, , of course of study php not care info different according whether developing, testing, demoing branch or operating live.

further reading: an first-class php deployment book, free of charge, suggests phing , capistrano.

php git netbeans github