This topic is locked

Project Organisation

4/4/2020 3:18:16 PM
PHPRunner General questions
T
thamestrader author

Just wondering how people organise version control for their projects.
I only have a single PHPR application. So my approach is as follows: In the PHPRunnerProjects folder I have a subfolder for each version. V6.0, v6.1 etc The first number increments every time the database table structure changes and the 2nd number increments everytime the code changes either for an enhancement or a bug fix. I have a customphp file for common functions in the source subfolder. The version number of this changes whenever it is amended.
When I build I have three subfolders DevOuput (my local testing) TrialOutput (User testing) and Live_yymmdd (so I can always revert or re-install without a build).
My question is this could I simplify this to subfolders per database version ie MY_AppV6, My_AppV7 etc and within those have multiple My_App*.phpr files i.e My_Appv61.phpr, My_Appv62.phpr etc one per version. I know I'd have to make sure that a customphp file was created for each new version of My_App. I thought this would work as PHPRunner only appears to save the phpr file.
Are thoughts or suggestions appreciated.
Norman

A
AlphaBase 4/5/2020

You might check this out:

Version Control

M
MikeT 4/5/2020

I'm also a single dev. I use subversion locally. I think it pays off to read a bit about the typical way how to work with subversion (or git if you want to use that), and the stick to it.

Basically the trunk, branch, tag concept for subversion. Then you's also now more need some self baked subfolder system.

The tools are free.

Sergey Kornilov admin 4/6/2020

I second and third the use of the source control system.

need2sleepDevClub member 4/6/2020

How much time does this add to your projects while working solo?
I think this is a great idea, especially if I need to contract out a piece of the project I'm not familiar with.