How to organize work on a Mac?

M

Maxim2012-08-04 15:16:51

git

Maxim, 2012-08-04 15:16:51

Hello
A week as the owner of a poppy and now I want to finally switch from Windows to poppy
. We work with a small team (2 programmers and a layout designer).

Tell me how you organize the work of your team:
editors, upload to production, dev server, git, database migration
Can someone combine development on Windows and Mac at the same time?
I have my own server

In recent days I have been reading so much that I can’t put it all in order
Thank you in advance

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

M

mr_idiot, 2012-08-04
@mr_idiot

You need to use editors, upload to production, of course everyone should have a dev server, it is desirable to use git, and, of course, migration frameworks.

M

Maxim, 2012-08-04
@websecret_by

As I understand it, upload it first to some kind of repository and then update it in production from there?

A

Anton Medvedev, 2012-08-04
@Elfet

We work on whatever we like: Mac, Windows, Ubuntu. GIT + GitHub + prod branch with auto-deploy to the server + trigger for automatic migration application.

N

northbear, 2012-08-04
@northbear

When working with git at the start, I recommend using the git-flow methodology. Look here on Habré there was a translation of the article “A successful Git branching model”.
For everything else, my advice is: don't get carried away with formalization/regulation. Give the team a chance to organize themselves. You should give them only the basic focus points on which they should concentrate. Use the Japanese principle. They build paths where people have trampled the paths the most. So do you, document only those rules that have already become the de facto standard. And remember the main goal of this formalization: It is needed to bring a new person to the team as quickly as possible. So that once again the newcomer does not have to chew on things that have long been historically established rules for the team.
For an effective team, formalization is not needed, or stupidly, it interferes ...

P

phasma, 2012-08-04
@phasma

Eclipse + local server -> mercurial -> scripts that perform changes to the database by cron, CSS/JS compression, etc. etc.
Everything works through hg, in your case it will be git, there is no fundamental difference. Then checkout on the server and everything starts. If there is time for tests, then run more tests before launching. I use Pyramid, there is a very good reload_templates option that allows you not to reload templates without restarting uwsgi.