The Shed is going Social! Join us on FaceBook and Twitter and chime in on the conversation.
|
 |
|
Dev Shed Forums
> Web Site Management
> Business Help
|
PHP-Security - How to share work of your website
Discuss How to share work of your website in the Business Help forum on Dev Shed. How to share work of your website Business Help forum discussing Business Documents, Copyright Law, Contracts, Non-Compete issues and more. Disclaimer: Always consult an attorney; this is just a place to discuss ideas.
|
|
 |
|
|
|
|

Dev Shed Forums Sponsor:
|
|
|

June 11th, 2011, 01:36 AM
|
|
Registered User
|
|
Join Date: May 2011
Posts: 21
Time spent in forums: 5 h 48 m 8 sec
Reputation Power: 0
|
|
|
PHP-Security - How to share work of your website
Hello....I have a query. I am developing a web application, perhaps a social networking site. Now, in order to spread it in the market, I need to have some developers with me. My site is following MVC architecture with observer design pattern.
So, how to share my work with them. Do I have to give my password to all of them. I mean, is it sensible to provide others the entire control of the app. What would you suggest??
|

June 11th, 2011, 03:01 AM
|
 |
Moderator Emeritus
|
|
Join Date: Feb 2002
Location: Scottsdale, AZ
|
|
|
Moved to Business Help from PHP, though Project Help Wanted might be a better option.
|

June 11th, 2011, 09:42 AM
|
 |
Lost in code
|
|
|
|
|
With a full scale web development project you generally have a live server, staging server, testing server and then a development machine for each developer that is working on the project.
Code is managed using version control, like SVN or GIT. Each developer has their own authentication details for this.
Not giving developers full access to the code will severely hurt their efficiency, and may make some tasks impossible for them to complete.
Generally the developers do not have access to the live or staging servers, but do have access to the testing server. However, it is often a good idea to give at least one developer access to the live and staging server so that they can debug problems that occur in the live environment but not in the testing or development environments.
|

June 11th, 2011, 09:48 PM
|
|
Registered User
|
|
Join Date: May 2011
Posts: 21
Time spent in forums: 5 h 48 m 8 sec
Reputation Power: 0
|
|
Quote: | Originally Posted by E-Oreo With a full scale web development project you generally have a live server, staging server, testing server and then a development machine for each developer that is working on the project.
Code is managed using version control, like SVN or GIT. Each developer has their own authentication details for this.
Not giving developers full access to the code will severely hurt their efficiency, and may make some tasks impossible for them to complete.
Generally the developers do not have access to the live or staging servers, but do have access to the testing server. However, it is often a good idea to give at least one developer access to the live and staging server so that they can debug problems that occur in the live environment but not in the testing or development environments. |
Thnx for the reply.. 
|
Developer Shed Advertisers and Affiliates
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate This Thread |
Linear Mode
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|