Note that there are some explanatory texts on larger screens.

plurals
  1. POWorkflow for webapplication development without local development servers using git(hub) 1 coder + 1 webdesigner
    primarykey
    data
    text
    <p>I am a programmer and in near future I am going to work together with a web/template designer on several projects. What do you think about my development workflow setup? Do you have any optimization tips?</p> <h1>Setup for one specific project</h1> <ul> <li>The whole project is hosted on github.</li> <li>The project is a complex webapplication running on a linux os (It's impossible to run it on a local development-server, neither on windows nor on mac).</li> <li>There are 2 branches: dev and master. dev is the testing server and master is the productive server.</li> <li>Besides from the main github repository there is a local repository on the designer's computer, one on my computer, one on the testserver and one on the production server.</li> <li>I develop locally (on Windows). While developing there is a auto-sync script that automatically uploads all files I edit via FTP to the testing server, so I can check instantly if my changes work.</li> <li>The designer also develops locally (on Mac), he will also have an auto-sync script that automatically uploads all his changes to the testserver via FTP, but he has just access to a special "layout"-directory where all templates and static files (images, css, js, ...) are located. He also needs to check every few minutes if his changes or new features work.</li> <li>Whenever the designer or me sucessfully finished and tested a new feature on the testserver we then push our changes from the local dev-branch to the remote dev-branch on github. The testing server is not touched by git so far.</li> <li>Everyday in the morning there is a cronjob, that deletes the whole testserver directory and then does a "git clone" of the dev-branch of the remote repository hosted on github. That way the testserver has all new commits.</li> <li>The designer and me have to "git pull" the newest updates of each other using the remote github repository every morning before any further development.</li> <li>As soon as a feature runs well on the testserver I will merge the "dev" branch to "master" and commit the master to github.</li> <li>Then we have a deployment that pulls the master branch from github to the production server.</li> </ul> <h1>Questions</h1> <p>How do you generally handle the situation where you cannot have local development-servers for each project-member (because the application is not able run locally)? It seems really unprofessional to have one testserver where everybody can upload files via ftp to try their stuff, because it can easily happen that someone overwrites someone elses files so testing will fail. Is there a best-practice example of how to develop in a team when there is no local testing server?</p> <p>Thanks in advance for you help and sorry about my english, its not my native language.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload