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 8 years ago.
Improve this question
We are building a new PHP project, and we heard of the new HHVM, we wanted to deploy our application on it, but we are not sure if it is ready for production environments or not?
We have a laravel 4 application with MySQL and MongoDB as the databases.
Our application is concerned alot about performance and speed of requests because it is a financial application.
Is HHVM production ready ? if it is not and we should wait, how easy will it be to migrate to it after we are live when it becomes production ready, will it break our code? and most of all will PHP be on HHVM for a good while after hack is in town ? is there any live examples of it (other than FB)?, We really like HHVMs performance, but we can't risk the whole project goin down after production.
I do not risk moving my current project to it yet, but I plan to enable CI-tests using HHVM (parallel to usual PHP-5.5 tests) really soon. This way I will know when the project is compatible and plan transition
My opinion:
I simply don't trust such a new one (Hack) and can't risk until it's become available or accepted by the community. It's not sure whether it'll gain trust or not. You are going to reduce the support for your project if you need any during the development, not enough resources and fellow developers, AFAIK.
I think, It's risky and you should think again about it. An article about Hack.
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 6 years ago.
Improve this question
What are the pros and cons of building your own web server, and the difference between building your own versus installing a 'pre-configured' web servers (such as: LAMP, WAMP, XAMPP, and other else). Is there any good benifits of building your own web server?
If you're gonna have your own server, would you rather build it on your own, or just download one from the internet? and Why?
Building your own web-server
Pros:
It will work exactly according to your taste
It will use the technologies of your choice
At the end you will know virtually everything about it, while with other webservers sometimes that is not possible
You will be famous if you implement something fantastic
Cons:
You will have to do a lot of complicated stuff which will delay the start of the task you wanted to work on in the first place
You on your own will not be capable to be even close to other webservers, developed by many programmers. You are one, they are legion
As times are changing, modern techniques will pour up and you will need to do a lot of work to adapt to the changes
Other webservers are free in many cases, while developing your webserver is very expensive: you pay with your sweat and tears
But the most important point is that before you start implementing your webserver try out others. Even if you reach to the conclusion that you want to write your own your experience with other webservers will help you a lot in planning yours.
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 7 years ago.
Improve this question
First of all I should remind you I have read some links and done some research and looked at some old questions but I still have a question.
I want to start a project with codeigniter 3 but I have heard that codeigniter is not secure enough!
I don't know if it is correct or not, so I started researching about it but now I still don't know. Should I start my project with codeigniter or not! I don't know how to work with any other frameworks and I don't have enough time so I want to ask you if I should start my project by codeigniter. Is it really unsafe? and what shall I do to make it secure or is it possible or not?
I know that the security depends on programmer but I want to be sure that codeigniter does not have a big security bug that any hacker can hack my project and destroy it.
what would you do ?
I'm really afraid
Codeigniter is a framework and is not solely responsible for your site's security. Your site's security is truely determined by the code you write with CodeIgniter. An empty CodeIgniter install is very, very secure. Simply because it's not using any user input or operating with any database.
Codeigniter 3 is no longer in beta and has a stable release available here: https://codeigniter.com/download
If your concern is security, make sure you develop the site with security best practices. Typically, if a site is hacked, it's due to a lazy developer and not the framework they were developing with.
along with security are all the million other things that can go wrong on the server or "cloud" which is hosting your application. so -- even if its just you working on the app -- become comfortable with git and version control. i just discovered the phpstorm application for developing php code and it has version control built in, along with other features that makes it easier to maintain more then one working copy of your application.
otherwise to your question - Codeigniter is being actively maintained, has a friendly community, and the code is very fast & stable in production.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm managing a team of 4 developers. We develop CMS based sites on a PHP / MySQL backend.
I want to improve the workflow. What i want:
Are there any services that host a git repo and sync it automatically with the servers?
Production server would be master branch
Testing server would be a different branch
we deal with many small sites and some large so we need workflow to be fast and agile
WHAT ABOUT THE DATABASE ? lol
(if anyone wants to add to the diagram PSD file can be found here: workflow.psd
I'd highly suggest using Beanstalk if you want something quick and easy to set up. It handles deployments very well. If you're looking at doing a bit more yourself (setting up the hooks and such) then another option would be github.
Please do not user Master as your production branch, master should never be production. A better workflow would be to have a Staging, Development, and Production branch / environment. Please see this guide about branching on Beanstalk's guides, it's pretty insightful.
As for keeping track of databases, if your framework / cms doesn't support database migration I'd highly suggest developing some form of migration / database version control in-house. You can also check out a framework like FuelPHP, which has migration built in. A nice little database version control system I found while poking around : dbv.php.