Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a product in its base version, and some of my clients demands some modifications that cannot be handled by plugin structure as it's not additional feature - but heavily modified version of some of core features. The problem is that we could handle applying bug-fixes for lets say two or three clients but now it is quite hard to handle and remember to apply same code changes in various projects.
The questions is: Is there methodology explaining how to handle such a problem, and how software like GIT or other SCMs could help me with it.
it is quite hard to handle and remember to apply same code changes in various projects.
git is perfect in your case. You can branch for each client and do the core modifications in the branchs. When it comes to apply bug fixes to every branch, you can either cherry-pick (a cool git feature) or rebase (another cool git feature) for each branch.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last year.
Improve this question
I am looking for a solution for code management in the company.
We have a lot of projects that we work on on a daily basis. And sometimes two developers are required to work on the same project simultaneously.
An optimal situation for us is that each developer will have his local environment. And when he updates his code, the changes will be updated by all developers automatically.
And so virtually all developers will have the constantly updated version.
The problem with GIT is that the upload/download has to be manual, so the developer may forget to download a version.
We work in a PC environment.
Please, inspire me :)
My employer had this same problem, and came to the conclusion that there is only one way to handle it:
Teach your developers to use git properly. Ideally, teach them some kind of system for branching and merging, such as git-flow or GitLab Flow.
Some git tools can help you by automatically querying the server every 10 minutes to see if someone else has pushed new commits and prompt you to download them. (I think VSCode has this feature, but I don't remember for sure. Personally, I use SmartGit which also has this feature.)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Sometimes a feature that I want to create for my laravel application already exists as a package.
It is easy to install them, but I am worried about their impact on the application performance.
What should I consider when choosing whether to install a package or develop a feature by myself?
It's personal preference at the end of the day.
Some packages are well written, optimized and maintained and this gives you so many benefits:
Reduced maintainence cost (i.e. you aren't 100% responsible for fixing the package code)
Decreased development time (i.e. you don't have to write it)
Increased functionality (i.e. they may have features you hadn't even thought of)
Other packages are poorly written, un-optimized and in some cases obsolete. These can have the opposite effect:
Increased maintainence cost (i.e. the author isn't neccesarily going to fix an issue)
Increased development time (i.e. you will probably have to learn their code base and fix issues yourself)
My advice would be to make sure that if it's a well respected author/company and their code base is activily being worked on (check github / npm / etc), then using the package will likely save you time and hassle in the long run.
You aren't likely to see any massive performance degredation by using composer packages over writing it yourself!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Currently, I'm working freelance and doing small projects (i.e. about 1 week to 1 month) for my customers. I use tools like FTP to upload/download files; setup a local web and database server for some projects; sometimes use Git or SVN for bigger projects. But most of the time, I just use FTP. This works just fine for me.
But now I'm planning to expand my work and may hire 1 or 2 programmers. Most of my works will be PHP/MySQL. What setting will be more suitable for my team? I goal is to minimize the configuration time.
Thank you.
While I'm not sure this is entirely suitable question for SO, and is quite open ended as plenty of people will have different solutions, here is one way of doing what you ask
Use Virtual Box & Vagrant along with Chef or Puppet to ensure all developers have identical development environments.
Then use Git via a central remote repo (i.e Github, BitBucket, custom) to collaborate.
If you have idea about GIT then Its better, you can make some more research there are some functions like branching, all of your team member can work on different branches and finally you can merge them
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Is there any mechanise, which can ensure that packages uploaded into packagist.org are free from malicious code.
Is anyone looking at source code in installed/uploaded packages.
For example: What if someone upload package which does main function and apart from that send my config file to external server?
When installation of packages is such easy as adding one line into composer.json I am bit worry that above situation can happen.
That's the blessing and curse of open source software. You typically have the entire source code available for inspection. This means it's pretty hard for anybody to include malicious code and have it remain undetected, though it's not a complete insurance against it. Gauge the vibe around the package, how many people are using it, what comments or tickets in the issue tracker say.
It comes down to: don't use software you don't trust. Trust it by evaluating it yourself or by trusting the community to have done so.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
When I am writing PHP i find it really hard to keep track of all the changes/bug fixes I make.
When you are creating a script in PHP what do you use to keep a track of any changes that you make along with adding version numbers and maintaining a changelog file?
Thanks in advance.
Use Versioning system. One of the most common is for example Subversion.
http://subversion.apache.org/
Subversion offers great features, like revision history, comparing between those revisions, also branching and tagging