Ok so how do multiple people work on the same website at once?

14 years ago

They will probably have a version control system (SVN, ClearCase etc) and a deployment administrator. The developers/coders do the changes and put the source into the version control system and then the deployment guy puts it onto the server. That way, not everyone gets access to the server.

I simplified it a lot. There would be many checks and balances to ensure things dont go wrong.

[ 1 ] Thanks
1 reply

{{ DiscussionBoard.errors[2704445].message }}

bgmacaw

14 years ago

Originally Posted by tvr

They will probably have a version control system (SVN, ClearCase etc) and a deployment administrator. The developers/coders do the changes and put the source into the version control system and then the deployment guy puts it onto the server. That way, not everyone gets access to the server.

Yes, this is the way things are done, more or less, in a professional software development environment.

Beyond just version control, normally you'll have one or more development servers where the development team can integrate their work beyond what they do on their own desktop. Next, there will be QA and Staging servers where the final working release can be tested and prepared for deployment. Lastly, there's the production server itself where the released version resides. Also, developers rarely have access to the production servers. In fact, for SOX compliance in the US, they aren't allowed to have access. Only designated administrators are allowed access.

[ 1 ] Thanks
1 reply

Signature

{{ DiscussionBoard.errors[2704561].message }}

MichaelHiles

14 years ago

Originally Posted by tvr

They will probably have a version control system (SVN, ClearCase etc) and a deployment administrator. The developers/coders do the changes and put the source into the version control system and then the deployment guy puts it onto the server. That way, not everyone gets access to the server.

I simplified it a lot. There would be many checks and balances to ensure things dont go wrong.

Originally Posted by bgmacaw

Yes, this is the way things are done, more or less, in a professional software development environment.

Beyond just version control, normally you'll have one or more development servers where the development team can integrate their work beyond what they do on their own desktop. Next, there will be QA and Staging servers where the final working release can be tested and prepared for deployment. Lastly, there's the production server itself where the released version resides. Also, developers rarely have access to the production servers. In fact, for SOX compliance in the US, they aren't allowed to have access. Only designated administrators are allowed access.

This. Source code control.

Our team uses Subversion and Microsoft Team Server. We have one person who is responsible for Quality Assurance... making sure that the delivered code meets the programming specifications. That person is the final sayso whether something gets moved from the test environment to production. It's tied to our proprietary software change request system that also has a customer-facing support request/ticketing front-end.

Thanks

Signature

10XTS... I got your digital strategy right here...

{{ DiscussionBoard.errors[2705733].message }}

alsmith1

14 years ago

Hi Kory,
You can actually log into your cpanel and assign different passwords for different users along with the rights(in other words, exactly what that person may and may not change), so this would allow someone else other than you to log in and do the task you have assigned them to do.

Hope this helps,

Allen

[ 1 ] Thanks
1 reply

{{ DiscussionBoard.errors[2704451].message }}

AFI

14 years ago

Originally Posted by alsmith1

Hi Kory,
You can actually log into your cpanel and assign different passwords for different users along with the rights(in other words, exactly what that person may and may not change), so this would allow someone else other than you to log in and do the task you have assigned them to do.

Hope this helps,

Allen

This is exactly it. You can add users to your CPanel that will allow other people to have as much access as you want to give them. Also like Google Analytics, you can also add users to see your reports too.

I also work for a huge PR6 website that has multiple workers doing different tasks on it and we all have our individual logins to the admin area and we each do different tasks.

[ 1 ] Thanks

Signature

Learn about Internet Marketing from my dofollow comment blog.....Make Extra Money At Home...
I WILL BUILD YOU YOUR OWN CUSTOM AMAZON REVIEW SITE - HUNDREDS SOLD!

{{ DiscussionBoard.errors[2704459].message }}

Steve Garratt

14 years ago

You don't do development on a live system like Facebook. It's too easy to screw it up. The software team will be working on one or more development servers or virtual machines for convenience. Site updates will be handles as tvr suggests.

[ 1 ] Thanks

Signature

Please visit my blog and if you have an interest in electronics then please join me at Home DIY Electronics

{{ DiscussionBoard.errors[2704574].message }}

sbucciarel

Banned 14 years ago

Operations like Facebook and other companies that have a lot of people working on a site have this:

They will probably have a version control system (SVN, ClearCase etc) and a deployment administrator.

There are programs that keep track of the changes made, keep copies of all versions and lock files that are being used so that no one else can edit them when someone is already editing them.

[ 1 ] Thanks

{{ DiscussionBoard.errors[2704582].message }}

Sam1985

14 years ago

There is simple fundamental for this is of client server model. there is the no. of users who are working in the same website is depends on their type of class of network.
Example: Class A, Class B, Class C, Class D and Class E networks.