TORTOISE: Dev Server, Production Server and Final client
up vote
0
down vote
favorite
I have two servers.
One is for developing and testing applications
The other is to release the software to production (We are a textile factory)
Right now, we finish the development and put the "final version" to the production server (drag and drop)
As you can imagine, this takes lots of times when we make an upgrade to the software. We need to drag and drop again, and sometimes the projects are big
So, I am looking for a solution that allows you to make a Commit at the developing server and then we can Upgrade the software at the production server.
Can I do that with SVN Tortoise?
Or maybe using Git?
git svn architecture tortoisesvn development-environment
add a comment |
up vote
0
down vote
favorite
I have two servers.
One is for developing and testing applications
The other is to release the software to production (We are a textile factory)
Right now, we finish the development and put the "final version" to the production server (drag and drop)
As you can imagine, this takes lots of times when we make an upgrade to the software. We need to drag and drop again, and sometimes the projects are big
So, I am looking for a solution that allows you to make a Commit at the developing server and then we can Upgrade the software at the production server.
Can I do that with SVN Tortoise?
Or maybe using Git?
git svn architecture tortoisesvn development-environment
1
I am not sure what you are asking about... Could please elaborate your complete question?
– royalTS
Nov 8 at 12:15
@royalTS I am sorry for the explanation. Hope its better now and thanks in advance
– Apeafa dez
Nov 8 at 13:19
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have two servers.
One is for developing and testing applications
The other is to release the software to production (We are a textile factory)
Right now, we finish the development and put the "final version" to the production server (drag and drop)
As you can imagine, this takes lots of times when we make an upgrade to the software. We need to drag and drop again, and sometimes the projects are big
So, I am looking for a solution that allows you to make a Commit at the developing server and then we can Upgrade the software at the production server.
Can I do that with SVN Tortoise?
Or maybe using Git?
git svn architecture tortoisesvn development-environment
I have two servers.
One is for developing and testing applications
The other is to release the software to production (We are a textile factory)
Right now, we finish the development and put the "final version" to the production server (drag and drop)
As you can imagine, this takes lots of times when we make an upgrade to the software. We need to drag and drop again, and sometimes the projects are big
So, I am looking for a solution that allows you to make a Commit at the developing server and then we can Upgrade the software at the production server.
Can I do that with SVN Tortoise?
Or maybe using Git?
git svn architecture tortoisesvn development-environment
git svn architecture tortoisesvn development-environment
edited Nov 8 at 13:57
asked Nov 8 at 10:34
Apeafa dez
83
83
1
I am not sure what you are asking about... Could please elaborate your complete question?
– royalTS
Nov 8 at 12:15
@royalTS I am sorry for the explanation. Hope its better now and thanks in advance
– Apeafa dez
Nov 8 at 13:19
add a comment |
1
I am not sure what you are asking about... Could please elaborate your complete question?
– royalTS
Nov 8 at 12:15
@royalTS I am sorry for the explanation. Hope its better now and thanks in advance
– Apeafa dez
Nov 8 at 13:19
1
1
I am not sure what you are asking about... Could please elaborate your complete question?
– royalTS
Nov 8 at 12:15
I am not sure what you are asking about... Could please elaborate your complete question?
– royalTS
Nov 8 at 12:15
@royalTS I am sorry for the explanation. Hope its better now and thanks in advance
– Apeafa dez
Nov 8 at 13:19
@royalTS I am sorry for the explanation. Hope its better now and thanks in advance
– Apeafa dez
Nov 8 at 13:19
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
I'm having some trouble parsing what you are asking, but let me give it a go:
You are looking to have something automatically build and deploy the production server when and if it is verified on the development server. This is not really a function of your version control software (SVN vs Git), but more the responsibility of your build process. Modern companies solve this with Continuous Integration (CI) and Continuous Delivery (CD) processes.
This is best handled through a CI/CD tool like Jenkins, although your ultimate solution strongly depends on what technical stack you are using (.NET? C++? Java?).
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I'm having some trouble parsing what you are asking, but let me give it a go:
You are looking to have something automatically build and deploy the production server when and if it is verified on the development server. This is not really a function of your version control software (SVN vs Git), but more the responsibility of your build process. Modern companies solve this with Continuous Integration (CI) and Continuous Delivery (CD) processes.
This is best handled through a CI/CD tool like Jenkins, although your ultimate solution strongly depends on what technical stack you are using (.NET? C++? Java?).
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
add a comment |
up vote
1
down vote
I'm having some trouble parsing what you are asking, but let me give it a go:
You are looking to have something automatically build and deploy the production server when and if it is verified on the development server. This is not really a function of your version control software (SVN vs Git), but more the responsibility of your build process. Modern companies solve this with Continuous Integration (CI) and Continuous Delivery (CD) processes.
This is best handled through a CI/CD tool like Jenkins, although your ultimate solution strongly depends on what technical stack you are using (.NET? C++? Java?).
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
add a comment |
up vote
1
down vote
up vote
1
down vote
I'm having some trouble parsing what you are asking, but let me give it a go:
You are looking to have something automatically build and deploy the production server when and if it is verified on the development server. This is not really a function of your version control software (SVN vs Git), but more the responsibility of your build process. Modern companies solve this with Continuous Integration (CI) and Continuous Delivery (CD) processes.
This is best handled through a CI/CD tool like Jenkins, although your ultimate solution strongly depends on what technical stack you are using (.NET? C++? Java?).
I'm having some trouble parsing what you are asking, but let me give it a go:
You are looking to have something automatically build and deploy the production server when and if it is verified on the development server. This is not really a function of your version control software (SVN vs Git), but more the responsibility of your build process. Modern companies solve this with Continuous Integration (CI) and Continuous Delivery (CD) processes.
This is best handled through a CI/CD tool like Jenkins, although your ultimate solution strongly depends on what technical stack you are using (.NET? C++? Java?).
answered Nov 8 at 15:38
Rob Conklin
4,717917
4,717917
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
add a comment |
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
We are using PHP So, we first develop an application in a Server A In that same server we test. When the application is ready we copy and paste the application to Server B So, imagine that two months later the client needs some change in the app. I will do the changes in Server A. But I only change two or three files. Is there a way that automatically I can send only the files I changed to Server B and not the entire project?
– Apeafa dez
Nov 8 at 15:49
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
You could let the version control do the heavy lifting. It would have the added benefit of allowing you to roll back fairly quickly. So, check the code out on the dev server... update it there and push it back to the SVN or Git server.. when you are done, check it out on the prod server.
– Rob Conklin
Nov 8 at 16:05
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
I would highly recommend you create a "Prod" branch so that merges are intentional.
– Rob Conklin
Nov 8 at 16:06
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53205919%2ftortoise-dev-server-production-server-and-final-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I am not sure what you are asking about... Could please elaborate your complete question?
– royalTS
Nov 8 at 12:15
@royalTS I am sorry for the explanation. Hope its better now and thanks in advance
– Apeafa dez
Nov 8 at 13:19