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?










share|improve this question




















  • 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















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?










share|improve this question




















  • 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













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?










share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








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














  • 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












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?).






share|improve this answer





















  • 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











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















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

























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?).






share|improve this answer





















  • 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















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?).






share|improve this answer





















  • 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













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?).






share|improve this answer












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?).







share|improve this answer












share|improve this answer



share|improve this answer










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


















  • 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


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














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





















































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







Popular posts from this blog

Schultheiß

Verwaltungsgliederung Dänemarks

Liste der Kulturdenkmale in Wilsdruff