What tools do you use when working with the backend??

Question

CMS

I am interested in exactly how you start working with the backend, what tools you use, cms, frameworks, etc. I would like to hear step by step, in two or three words. I will be very grateful for adequate answers. Thank you!

Answer 1

1. git repository
2. vagrant + ansible for setting up the environment (php 5.6, postgresql 9.4, nginx and then what is needed specifically for the project)
3. basic application framework based on symfony2 (the structure has been slightly changed for itself)
4. behat, phpspec - basic settings
5. phpcpd, phpmd, php-cs-fixer and other gadgets for automatic code analysis and report generation
5. gulp - for building backend and frontend
6. angular application skeleton for admin panel
In order not to go crazy, almost everything is done within the framework of the basic framework of the application, and then it is already finished for the project.
7. generating keys for deployment and encrypting them in gpg with developer and CI keys (if necessary)
8. setting up CI
Well, then there are rallies, discussions, and coding itself

Answer 2

> I would like to hear step by step , in two or three words

1 - you need a project framework, you can usually use a framework framework
2 - if the project is small or medium, do not use menstrual frameworks like yii2 or symfony2, you will have more problems
3 - git, intellij, sourcetree, sublime, zsh, vagrant + ansible, gulp
4 - simple start doing a project, when you need something, be it isolation, fast portability from machine to machine, it is possible not to install the project for 7 days or not to assemble it for 8 hours, you will reach everything yourself

Answer 3

I use my own development (a framework, I did it myself in pure PHP + completely my own .htaccess to protect against most of the "crooked" requests), my own ORM and FORM-builder; I use Far for editing, I use ionCube to "protect" (well, everything is clear, at least somehow...) of my applications.
If you are interested in details - in a personal.

Answer 4

1. git repository
2. vagrant environment
3. directory framework
4. autotest environment
5. connecting CI system
6. README.md
--
7. you can already code

Answer 5

CleverStyle CMS for development, as a result, many things are done very simply, for example, there is no project build process, since the engine itself does this.
PhpStorm with configured File Watchers - I write SCSS, CoffeeScript, HAML, I immediately get CSS, JS, HTML, very convenient.
Git for version control and deployment (by git push production, a hard reset is done on the server).
Production recently under Docker, made a special set of containers for this business, which link and work together: docker-webserver It is very useful to connect SensioLabInsights and Scrutinizer for static analysis in addition to what is in the IDE, finds and suggests a lot, Travis CI to run tests on every commit.
docker Well, the environment is similar to production.