Ttdfjt

Why do we need a bootloader separate than our application program in MCU's?

How to deal with administrative duties killing the research spirit?

Is it possible to spoof an IP address to an exact number?

Contributing to a candidate as a Foreign National US Resident?

Did Stalin kill all Soviet officers involved in the Winter War?

Data normalization before or after train-test split?

What is the meaning of "то, что он пишет"?

Has there ever been a cold war other than between the U.S. and the U.S.S.R.?

About opening an LLC with little to report in the beginning

Will electrically joined dipoles of different lengths, at right angles, behave as a multiband antenna?

Taking advantage when the HR forgets to communicate the rules

PhD: When to quit and move on?

Two queries on triangles, the sides of which have rational lengths

Motorcyle Chain needs to be cleaned every time you lube it?

Platform Event Design when Subscribers are Apex Triggers

What happens if the limit of 4 billion files was exceeded in an ext4 partition?

Do the 26 richest billionaires own as much wealth as the poorest 3.8 billion people?

What units are kpts?

What instances can be solved today by modern solvers (pure LP)?

Machine Learning Golf: Multiplication

Why did the "Orks" never develop better firearms than Firelances and Handcannons?

What does the ash content of broken wheat really mean?

What/Where usage English vs Japanese

What is exact meaning of “ich wäre gern”?

Best way to work on Magento 2

What is the best way to transfer Magento setup to another folder?Looking for some help setting up MagentoBest way to setup magento 2 on virtualbox as shared folderGetting 404 Error on Second Domain - Magento 2 Multi-StoreBest server setup for Magento 2Magento 2 and git, best practice for custom module developmentMagento 2 and Mail ConfigurationMagento2 | Which procedure to upgrade to 2.2.6 in area development / GIT?Magento 2 Duplicate product does not workM2 | How can we use same code base among all team members via Git?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

We have dedicated server Magneto 2 and we don't have cPanel or Plesk interface.
We have staging and Live websites.

Please suggest what is the best way of working with Magneto 2.

I feel Our Developers are making changes directly on Live server and whenever something went wrong they just roll back the whole website which is causing more issues.

We need to know the professional way of working with Dedicated Magneto Server.

How developer should work?

Should they work on live site or keep the code in Git???

Please explain

magento2 server-setup developer-mode github

share|improve this question

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

add a comment | 

0

We have dedicated server Magneto 2 and we don't have cPanel or Plesk interface.
We have staging and Live websites.

Please suggest what is the best way of working with Magneto 2.

I feel Our Developers are making changes directly on Live server and whenever something went wrong they just roll back the whole website which is causing more issues.

We need to know the professional way of working with Dedicated Magneto Server.

How developer should work?

Should they work on live site or keep the code in Git???

Please explain

magento2 server-setup developer-mode github

share|improve this question

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

add a comment | 

We have dedicated server Magneto 2 and we don't have cPanel or Plesk interface.
We have staging and Live websites.

Please suggest what is the best way of working with Magneto 2.

I feel Our Developers are making changes directly on Live server and whenever something went wrong they just roll back the whole website which is causing more issues.

We need to know the professional way of working with Dedicated Magneto Server.

How developer should work?

Should they work on live site or keep the code in Git???

Please explain

magento2 server-setup developer-mode github

share|improve this question

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

share|improve this question

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

share|improve this question

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

edited Jun 25 at 20:39

Dominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

asked Jun 25 at 15:47

Rachna ThakurRachna Thakur

4166 bronze badges

1 Answer
1

active

oldest

votes

1

Depends on the size of the build and the budget for dev resources. But on a larger site we have 3 sites. And a lot of these are a topic in their own right. The most solid setup is to have three sites.

Dev

This can be local or shared. If shared typical sftp access. Changes are tracked in git. Try to use something like git flow to enable multiple devs work on the site at the same time. If working local something like docker.

Staging

Client has acess to the site. But locked down to outside world. This site is often used to get work signed off before going live. My team has mixed feelings about staging site but I prefer to have deployment configured. There's lots of different ways in which this can be done but basically pushing to master in git on a particular remote will trigger a deployment process which triggers magento processes to upgrade and deploy static content. It's useful for staging site to have near live data but to help debugging but not necessary.

Live

Deployment configured. Production master remote triggers deployment. Caches on. Open to public. Only approved changes are put live. Larger updates are put live outside of busy periods.

Sorry all a bit vague. But this is a huge topic.

But yes changes in git and no not on a live site. But nobody is perfect and we've all had to do a bit of debugging on live site because of unexpected condition. Magento is complex and at times unpredictable.

share|improve this answer

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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

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

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f279576%2fbest-way-to-work-on-magento-2%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

1

Depends on the size of the build and the budget for dev resources. But on a larger site we have 3 sites. And a lot of these are a topic in their own right. The most solid setup is to have three sites.

Dev

This can be local or shared. If shared typical sftp access. Changes are tracked in git. Try to use something like git flow to enable multiple devs work on the site at the same time. If working local something like docker.

Staging

Client has acess to the site. But locked down to outside world. This site is often used to get work signed off before going live. My team has mixed feelings about staging site but I prefer to have deployment configured. There's lots of different ways in which this can be done but basically pushing to master in git on a particular remote will trigger a deployment process which triggers magento processes to upgrade and deploy static content. It's useful for staging site to have near live data but to help debugging but not necessary.

Live

Deployment configured. Production master remote triggers deployment. Caches on. Open to public. Only approved changes are put live. Larger updates are put live outside of busy periods.

Sorry all a bit vague. But this is a huge topic.

But yes changes in git and no not on a live site. But nobody is perfect and we've all had to do a bit of debugging on live site because of unexpected condition. Magento is complex and at times unpredictable.

share|improve this answer

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

add a comment | 

1

Depends on the size of the build and the budget for dev resources. But on a larger site we have 3 sites. And a lot of these are a topic in their own right. The most solid setup is to have three sites.

Dev

This can be local or shared. If shared typical sftp access. Changes are tracked in git. Try to use something like git flow to enable multiple devs work on the site at the same time. If working local something like docker.

Staging

Client has acess to the site. But locked down to outside world. This site is often used to get work signed off before going live. My team has mixed feelings about staging site but I prefer to have deployment configured. There's lots of different ways in which this can be done but basically pushing to master in git on a particular remote will trigger a deployment process which triggers magento processes to upgrade and deploy static content. It's useful for staging site to have near live data but to help debugging but not necessary.

Live

Deployment configured. Production master remote triggers deployment. Caches on. Open to public. Only approved changes are put live. Larger updates are put live outside of busy periods.

Sorry all a bit vague. But this is a huge topic.

But yes changes in git and no not on a live site. But nobody is perfect and we've all had to do a bit of debugging on live site because of unexpected condition. Magento is complex and at times unpredictable.

share|improve this answer

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

add a comment | 

Depends on the size of the build and the budget for dev resources. But on a larger site we have 3 sites. And a lot of these are a topic in their own right. The most solid setup is to have three sites.

Dev

This can be local or shared. If shared typical sftp access. Changes are tracked in git. Try to use something like git flow to enable multiple devs work on the site at the same time. If working local something like docker.

Staging

Client has acess to the site. But locked down to outside world. This site is often used to get work signed off before going live. My team has mixed feelings about staging site but I prefer to have deployment configured. There's lots of different ways in which this can be done but basically pushing to master in git on a particular remote will trigger a deployment process which triggers magento processes to upgrade and deploy static content. It's useful for staging site to have near live data but to help debugging but not necessary.

Live

Deployment configured. Production master remote triggers deployment. Caches on. Open to public. Only approved changes are put live. Larger updates are put live outside of busy periods.

Sorry all a bit vague. But this is a huge topic.

But yes changes in git and no not on a live site. But nobody is perfect and we've all had to do a bit of debugging on live site because of unexpected condition. Magento is complex and at times unpredictable.

share|improve this answer

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

share|improve this answer

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges

answered Jun 25 at 19:21

Dominic XigenDominic Xigen

2,31011 gold badge33 silver badges1414 bronze badges