Best practice for local development Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is the best IDE for Magento development?best practice for placing descriptions and landing pagesBest Practice for staging/development siteMagento2: Best practice to modify css filesSetting up a local development environment on xampp for magentoMagento 2 local development environmentBest practice for location of a classMagento 2 best practice for class locations and namesTesting/Development Environment on local serverMagento 2 and git, best practice for custom module development
In musical terms, what properties are varied by the human voice to produce different words / syllables?
The test team as an enemy of development? And how can this be avoided?
What does it mean that physics no longer uses mechanical models to describe phenomena?
How can god fight other gods?
How to align enumerate environment inside description environment
What does the writing on Poe's helmet say?
Is it dangerous to install hacking tools on my private linux machine?
Why is std::move not [[nodiscard]] in C++20?
Sally's older brother
Constant factor of an array
What is the difference between a "ranged attack" and a "ranged weapon attack"?
Can you force honesty by using the Speak with Dead and Zone of Truth spells together?
Did pre-Columbian Americans know the spherical shape of the Earth?
How does light 'choose' between wave and particle behaviour?
Moving a wrapfig vertically to encroach partially on a subsection title
Is there public access to the Meteor Crater in Arizona?
Does the Black Tentacles spell do damage twice at the start of turn to an already restrained creature?
Does silver oxide react with hydrogen sulfide?
Simple Line in LaTeX Help!
Why are vacuum tubes still used in amateur radios?
What are the main differences between the original Stargate SG-1 and the Final Cut edition?
What would you call this weird metallic apparatus that allows you to lift people?
What is the origin of 落第?
What does 丫 mean? 丫是什么意思?
Best practice for local development
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?What is the best IDE for Magento development?best practice for placing descriptions and landing pagesBest Practice for staging/development siteMagento2: Best practice to modify css filesSetting up a local development environment on xampp for magentoMagento 2 local development environmentBest practice for location of a classMagento 2 best practice for class locations and namesTesting/Development Environment on local serverMagento 2 and git, best practice for custom module development
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I've been trying to find the best way on how to develop a Magento 2 webshop locally. So far, I had no luck: lots of JS, CSS and 404 errors (on which I tried lots of fixes which only partly solved my problems).
My question is:
What is the best (step by step) way to develop a Magento 2 webshop locally (and if possible, 100% error free after installation)?
The Magento 2 dev docs don't really provide a comprehensive guide on how to do this.
I prefer using Laragon over XAMPP: it works way better and has lots of customization options including localhost URL's like webshop.dev
instead of localhost/webshop
.
FYI: I currently use Windows at home, but in the future I am planning to buy a Mac, but for now I'd like to know how I can do this the best way possible on a Windows machine (or a universal way).
magento2 best-practice development local
add a comment |
I've been trying to find the best way on how to develop a Magento 2 webshop locally. So far, I had no luck: lots of JS, CSS and 404 errors (on which I tried lots of fixes which only partly solved my problems).
My question is:
What is the best (step by step) way to develop a Magento 2 webshop locally (and if possible, 100% error free after installation)?
The Magento 2 dev docs don't really provide a comprehensive guide on how to do this.
I prefer using Laragon over XAMPP: it works way better and has lots of customization options including localhost URL's like webshop.dev
instead of localhost/webshop
.
FYI: I currently use Windows at home, but in the future I am planning to buy a Mac, but for now I'd like to know how I can do this the best way possible on a Windows machine (or a universal way).
magento2 best-practice development local
add a comment |
I've been trying to find the best way on how to develop a Magento 2 webshop locally. So far, I had no luck: lots of JS, CSS and 404 errors (on which I tried lots of fixes which only partly solved my problems).
My question is:
What is the best (step by step) way to develop a Magento 2 webshop locally (and if possible, 100% error free after installation)?
The Magento 2 dev docs don't really provide a comprehensive guide on how to do this.
I prefer using Laragon over XAMPP: it works way better and has lots of customization options including localhost URL's like webshop.dev
instead of localhost/webshop
.
FYI: I currently use Windows at home, but in the future I am planning to buy a Mac, but for now I'd like to know how I can do this the best way possible on a Windows machine (or a universal way).
magento2 best-practice development local
I've been trying to find the best way on how to develop a Magento 2 webshop locally. So far, I had no luck: lots of JS, CSS and 404 errors (on which I tried lots of fixes which only partly solved my problems).
My question is:
What is the best (step by step) way to develop a Magento 2 webshop locally (and if possible, 100% error free after installation)?
The Magento 2 dev docs don't really provide a comprehensive guide on how to do this.
I prefer using Laragon over XAMPP: it works way better and has lots of customization options including localhost URL's like webshop.dev
instead of localhost/webshop
.
FYI: I currently use Windows at home, but in the future I am planning to buy a Mac, but for now I'd like to know how I can do this the best way possible on a Windows machine (or a universal way).
magento2 best-practice development local
magento2 best-practice development local
edited Jun 26 '18 at 14:04
Bram
asked Jun 26 '18 at 13:43
BramBram
315121
315121
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
Your question is quite broad, so hard to give an exact answer without me spending ages on a reply - but using anything like XAMPP is a bad idea from the start (I know from experience) especially with Magento.
My preferred way is to use a virtual machine running Linux - in my case Ubuntu 16.04LTS server edition (as it's the same as my production server)
Virtualbox is free - https://www.virtualbox.org/wiki/Downloads
On this virtualbox, I install nginx, php7.0-fpm etc. (as per the Magento 2 devdocs) and configure in the same manner as my production/staging servers. I'd then make a host entry in Windows that points my 'dev domain' to the virtualbox IP.
I then use n98-magerun to export a 'developer' version of my production database, a must to avoid customer data being present on your local machine (GDPR, best practices)
Mount a folder from your virtualbox into windows, you can then open this folder in an editor such as atom to work on your project.
If you work this way, then you'll have no issues when you move to Mac also, as you can work on Mac, Linux or Windows. Your virtual machine image can always be the same, and as your production and staging servers with no nasty surprises when deploying. I recommend git for deployment and general version control also.
Larger companies also use things like docker, this lets you spin up a magento instance in its own container from an image - more portable than virtualbox, but virtualbox will fit your need just fine in my opinion.
Summary
- Use same OS as your production/staging servers.
- Use same PHP versions as production/staging.
- Ensure to cleanse data from production db
- Avoid one click install solutions, you'll learn way more about Magento by doing your own deployments.
If you have any questions, let me know and I will try to elaborate in my answer :)
I will try it out !
– Bram
Jun 28 '18 at 6:42
add a comment |
If you want a ready to use environment take a look to https://github.com/paliarush/magento2-vagrant-for-developers
Will try it out!
– Bram
Jun 28 '18 at 6:42
add a comment |
I just recently wrote a tutorial on this. With Docker, you can mimic just about any production environment. It’s modular and there is lots of support for it.
Docker / Magento 2
I should note that at my full time job as a Magento Tech Lead I am constantly configuring a variety of Docker environments to match production environments. You can add Redis, RabbitMQ, Elasticsearch and so much more. If I was slightly nerdier I’d get the whale tattoo just beneath the Magento tattoo.
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
1
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
1
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
add a comment |
The only problem with Laragon (Windows) is that you need to use the Copy method over Symlink and by doing this everything fails first.
app/etc/di.xml
<item name="view_preprocessed" xsi:type="object">MagentoFrameworkAppViewAssetMaterializationStrategyCopy</item>
Another fix that you need is the "backslash" -fix
#/vendor/magento/framework/View/Element/Template/File/Validator.php
From this file line: 114
$realPath = $this->fileDriver->getRealPath($path);
to
$realPath = str_replace('\', '/', $this->fileDriver->getRealPath($path));
After a couple of refreshes every file is properly copied and available before timeout.
I really can't think any reason why you can not develop in Windows with Laragon because all you need to modify is inside /app/ -folder. Any modifications inside /vendor/ -folder is done via composer.
...and i have to say that Laragon is still the fastest and easiest thing that i've come across. The GUI is unbelievable good. Magento installs in no time and you have all the tools that you ever going to need available by no time without the need to open hardly any editor.
add a comment |
Running the Bitnami Magento 2 image in Oracle Virtual Box is a lot quicker than Xampp on Windows in my experience
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
);
);
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%2fmagento.stackexchange.com%2fquestions%2f231412%2fbest-practice-for-local-development%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your question is quite broad, so hard to give an exact answer without me spending ages on a reply - but using anything like XAMPP is a bad idea from the start (I know from experience) especially with Magento.
My preferred way is to use a virtual machine running Linux - in my case Ubuntu 16.04LTS server edition (as it's the same as my production server)
Virtualbox is free - https://www.virtualbox.org/wiki/Downloads
On this virtualbox, I install nginx, php7.0-fpm etc. (as per the Magento 2 devdocs) and configure in the same manner as my production/staging servers. I'd then make a host entry in Windows that points my 'dev domain' to the virtualbox IP.
I then use n98-magerun to export a 'developer' version of my production database, a must to avoid customer data being present on your local machine (GDPR, best practices)
Mount a folder from your virtualbox into windows, you can then open this folder in an editor such as atom to work on your project.
If you work this way, then you'll have no issues when you move to Mac also, as you can work on Mac, Linux or Windows. Your virtual machine image can always be the same, and as your production and staging servers with no nasty surprises when deploying. I recommend git for deployment and general version control also.
Larger companies also use things like docker, this lets you spin up a magento instance in its own container from an image - more portable than virtualbox, but virtualbox will fit your need just fine in my opinion.
Summary
- Use same OS as your production/staging servers.
- Use same PHP versions as production/staging.
- Ensure to cleanse data from production db
- Avoid one click install solutions, you'll learn way more about Magento by doing your own deployments.
If you have any questions, let me know and I will try to elaborate in my answer :)
I will try it out !
– Bram
Jun 28 '18 at 6:42
add a comment |
Your question is quite broad, so hard to give an exact answer without me spending ages on a reply - but using anything like XAMPP is a bad idea from the start (I know from experience) especially with Magento.
My preferred way is to use a virtual machine running Linux - in my case Ubuntu 16.04LTS server edition (as it's the same as my production server)
Virtualbox is free - https://www.virtualbox.org/wiki/Downloads
On this virtualbox, I install nginx, php7.0-fpm etc. (as per the Magento 2 devdocs) and configure in the same manner as my production/staging servers. I'd then make a host entry in Windows that points my 'dev domain' to the virtualbox IP.
I then use n98-magerun to export a 'developer' version of my production database, a must to avoid customer data being present on your local machine (GDPR, best practices)
Mount a folder from your virtualbox into windows, you can then open this folder in an editor such as atom to work on your project.
If you work this way, then you'll have no issues when you move to Mac also, as you can work on Mac, Linux or Windows. Your virtual machine image can always be the same, and as your production and staging servers with no nasty surprises when deploying. I recommend git for deployment and general version control also.
Larger companies also use things like docker, this lets you spin up a magento instance in its own container from an image - more portable than virtualbox, but virtualbox will fit your need just fine in my opinion.
Summary
- Use same OS as your production/staging servers.
- Use same PHP versions as production/staging.
- Ensure to cleanse data from production db
- Avoid one click install solutions, you'll learn way more about Magento by doing your own deployments.
If you have any questions, let me know and I will try to elaborate in my answer :)
I will try it out !
– Bram
Jun 28 '18 at 6:42
add a comment |
Your question is quite broad, so hard to give an exact answer without me spending ages on a reply - but using anything like XAMPP is a bad idea from the start (I know from experience) especially with Magento.
My preferred way is to use a virtual machine running Linux - in my case Ubuntu 16.04LTS server edition (as it's the same as my production server)
Virtualbox is free - https://www.virtualbox.org/wiki/Downloads
On this virtualbox, I install nginx, php7.0-fpm etc. (as per the Magento 2 devdocs) and configure in the same manner as my production/staging servers. I'd then make a host entry in Windows that points my 'dev domain' to the virtualbox IP.
I then use n98-magerun to export a 'developer' version of my production database, a must to avoid customer data being present on your local machine (GDPR, best practices)
Mount a folder from your virtualbox into windows, you can then open this folder in an editor such as atom to work on your project.
If you work this way, then you'll have no issues when you move to Mac also, as you can work on Mac, Linux or Windows. Your virtual machine image can always be the same, and as your production and staging servers with no nasty surprises when deploying. I recommend git for deployment and general version control also.
Larger companies also use things like docker, this lets you spin up a magento instance in its own container from an image - more portable than virtualbox, but virtualbox will fit your need just fine in my opinion.
Summary
- Use same OS as your production/staging servers.
- Use same PHP versions as production/staging.
- Ensure to cleanse data from production db
- Avoid one click install solutions, you'll learn way more about Magento by doing your own deployments.
If you have any questions, let me know and I will try to elaborate in my answer :)
Your question is quite broad, so hard to give an exact answer without me spending ages on a reply - but using anything like XAMPP is a bad idea from the start (I know from experience) especially with Magento.
My preferred way is to use a virtual machine running Linux - in my case Ubuntu 16.04LTS server edition (as it's the same as my production server)
Virtualbox is free - https://www.virtualbox.org/wiki/Downloads
On this virtualbox, I install nginx, php7.0-fpm etc. (as per the Magento 2 devdocs) and configure in the same manner as my production/staging servers. I'd then make a host entry in Windows that points my 'dev domain' to the virtualbox IP.
I then use n98-magerun to export a 'developer' version of my production database, a must to avoid customer data being present on your local machine (GDPR, best practices)
Mount a folder from your virtualbox into windows, you can then open this folder in an editor such as atom to work on your project.
If you work this way, then you'll have no issues when you move to Mac also, as you can work on Mac, Linux or Windows. Your virtual machine image can always be the same, and as your production and staging servers with no nasty surprises when deploying. I recommend git for deployment and general version control also.
Larger companies also use things like docker, this lets you spin up a magento instance in its own container from an image - more portable than virtualbox, but virtualbox will fit your need just fine in my opinion.
Summary
- Use same OS as your production/staging servers.
- Use same PHP versions as production/staging.
- Ensure to cleanse data from production db
- Avoid one click install solutions, you'll learn way more about Magento by doing your own deployments.
If you have any questions, let me know and I will try to elaborate in my answer :)
answered Jun 26 '18 at 17:04
Ricky Odin MatthewsRicky Odin Matthews
816512
816512
I will try it out !
– Bram
Jun 28 '18 at 6:42
add a comment |
I will try it out !
– Bram
Jun 28 '18 at 6:42
I will try it out !
– Bram
Jun 28 '18 at 6:42
I will try it out !
– Bram
Jun 28 '18 at 6:42
add a comment |
If you want a ready to use environment take a look to https://github.com/paliarush/magento2-vagrant-for-developers
Will try it out!
– Bram
Jun 28 '18 at 6:42
add a comment |
If you want a ready to use environment take a look to https://github.com/paliarush/magento2-vagrant-for-developers
Will try it out!
– Bram
Jun 28 '18 at 6:42
add a comment |
If you want a ready to use environment take a look to https://github.com/paliarush/magento2-vagrant-for-developers
If you want a ready to use environment take a look to https://github.com/paliarush/magento2-vagrant-for-developers
answered Jun 26 '18 at 17:15
LorenzoLorenzo
410415
410415
Will try it out!
– Bram
Jun 28 '18 at 6:42
add a comment |
Will try it out!
– Bram
Jun 28 '18 at 6:42
Will try it out!
– Bram
Jun 28 '18 at 6:42
Will try it out!
– Bram
Jun 28 '18 at 6:42
add a comment |
I just recently wrote a tutorial on this. With Docker, you can mimic just about any production environment. It’s modular and there is lots of support for it.
Docker / Magento 2
I should note that at my full time job as a Magento Tech Lead I am constantly configuring a variety of Docker environments to match production environments. You can add Redis, RabbitMQ, Elasticsearch and so much more. If I was slightly nerdier I’d get the whale tattoo just beneath the Magento tattoo.
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
1
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
1
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
add a comment |
I just recently wrote a tutorial on this. With Docker, you can mimic just about any production environment. It’s modular and there is lots of support for it.
Docker / Magento 2
I should note that at my full time job as a Magento Tech Lead I am constantly configuring a variety of Docker environments to match production environments. You can add Redis, RabbitMQ, Elasticsearch and so much more. If I was slightly nerdier I’d get the whale tattoo just beneath the Magento tattoo.
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
1
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
1
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
add a comment |
I just recently wrote a tutorial on this. With Docker, you can mimic just about any production environment. It’s modular and there is lots of support for it.
Docker / Magento 2
I should note that at my full time job as a Magento Tech Lead I am constantly configuring a variety of Docker environments to match production environments. You can add Redis, RabbitMQ, Elasticsearch and so much more. If I was slightly nerdier I’d get the whale tattoo just beneath the Magento tattoo.
I just recently wrote a tutorial on this. With Docker, you can mimic just about any production environment. It’s modular and there is lots of support for it.
Docker / Magento 2
I should note that at my full time job as a Magento Tech Lead I am constantly configuring a variety of Docker environments to match production environments. You can add Redis, RabbitMQ, Elasticsearch and so much more. If I was slightly nerdier I’d get the whale tattoo just beneath the Magento tattoo.
answered Jun 27 '18 at 4:31
Shawn AbramsonShawn Abramson
2,4971915
2,4971915
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
1
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
1
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
add a comment |
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
1
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
1
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
Hmm this sounds very interesting. Will try it out on the Mac I use on my intern (because it requires Windows 10 Pro, I have Windows 10 Home...). I'll come back to you!
– Bram
Jun 28 '18 at 6:42
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
I can't get pass the create project part at the beginning. It throws an error saying it requires mcrypt but since I have php 7.1.7 installed, mcrypt has become deprecated. I tried to downgrade to php 7.0 but no luck yet
– Bram
Jun 28 '18 at 9:37
1
1
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
When running composer create or composer update, try adding the —ignore-platform-reqs flag.
– Shawn Abramson
Jun 28 '18 at 12:03
1
1
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
That flag tells composer not to look at the php extensions installed on your host system bc it’s the php inside of docker that’s going to power the site
– Shawn Abramson
Jun 28 '18 at 12:05
add a comment |
The only problem with Laragon (Windows) is that you need to use the Copy method over Symlink and by doing this everything fails first.
app/etc/di.xml
<item name="view_preprocessed" xsi:type="object">MagentoFrameworkAppViewAssetMaterializationStrategyCopy</item>
Another fix that you need is the "backslash" -fix
#/vendor/magento/framework/View/Element/Template/File/Validator.php
From this file line: 114
$realPath = $this->fileDriver->getRealPath($path);
to
$realPath = str_replace('\', '/', $this->fileDriver->getRealPath($path));
After a couple of refreshes every file is properly copied and available before timeout.
I really can't think any reason why you can not develop in Windows with Laragon because all you need to modify is inside /app/ -folder. Any modifications inside /vendor/ -folder is done via composer.
...and i have to say that Laragon is still the fastest and easiest thing that i've come across. The GUI is unbelievable good. Magento installs in no time and you have all the tools that you ever going to need available by no time without the need to open hardly any editor.
add a comment |
The only problem with Laragon (Windows) is that you need to use the Copy method over Symlink and by doing this everything fails first.
app/etc/di.xml
<item name="view_preprocessed" xsi:type="object">MagentoFrameworkAppViewAssetMaterializationStrategyCopy</item>
Another fix that you need is the "backslash" -fix
#/vendor/magento/framework/View/Element/Template/File/Validator.php
From this file line: 114
$realPath = $this->fileDriver->getRealPath($path);
to
$realPath = str_replace('\', '/', $this->fileDriver->getRealPath($path));
After a couple of refreshes every file is properly copied and available before timeout.
I really can't think any reason why you can not develop in Windows with Laragon because all you need to modify is inside /app/ -folder. Any modifications inside /vendor/ -folder is done via composer.
...and i have to say that Laragon is still the fastest and easiest thing that i've come across. The GUI is unbelievable good. Magento installs in no time and you have all the tools that you ever going to need available by no time without the need to open hardly any editor.
add a comment |
The only problem with Laragon (Windows) is that you need to use the Copy method over Symlink and by doing this everything fails first.
app/etc/di.xml
<item name="view_preprocessed" xsi:type="object">MagentoFrameworkAppViewAssetMaterializationStrategyCopy</item>
Another fix that you need is the "backslash" -fix
#/vendor/magento/framework/View/Element/Template/File/Validator.php
From this file line: 114
$realPath = $this->fileDriver->getRealPath($path);
to
$realPath = str_replace('\', '/', $this->fileDriver->getRealPath($path));
After a couple of refreshes every file is properly copied and available before timeout.
I really can't think any reason why you can not develop in Windows with Laragon because all you need to modify is inside /app/ -folder. Any modifications inside /vendor/ -folder is done via composer.
...and i have to say that Laragon is still the fastest and easiest thing that i've come across. The GUI is unbelievable good. Magento installs in no time and you have all the tools that you ever going to need available by no time without the need to open hardly any editor.
The only problem with Laragon (Windows) is that you need to use the Copy method over Symlink and by doing this everything fails first.
app/etc/di.xml
<item name="view_preprocessed" xsi:type="object">MagentoFrameworkAppViewAssetMaterializationStrategyCopy</item>
Another fix that you need is the "backslash" -fix
#/vendor/magento/framework/View/Element/Template/File/Validator.php
From this file line: 114
$realPath = $this->fileDriver->getRealPath($path);
to
$realPath = str_replace('\', '/', $this->fileDriver->getRealPath($path));
After a couple of refreshes every file is properly copied and available before timeout.
I really can't think any reason why you can not develop in Windows with Laragon because all you need to modify is inside /app/ -folder. Any modifications inside /vendor/ -folder is done via composer.
...and i have to say that Laragon is still the fastest and easiest thing that i've come across. The GUI is unbelievable good. Magento installs in no time and you have all the tools that you ever going to need available by no time without the need to open hardly any editor.
answered Mar 11 at 17:52
HelppoelämäHelppoelämä
164
164
add a comment |
add a comment |
Running the Bitnami Magento 2 image in Oracle Virtual Box is a lot quicker than Xampp on Windows in my experience
add a comment |
Running the Bitnami Magento 2 image in Oracle Virtual Box is a lot quicker than Xampp on Windows in my experience
add a comment |
Running the Bitnami Magento 2 image in Oracle Virtual Box is a lot quicker than Xampp on Windows in my experience
Running the Bitnami Magento 2 image in Oracle Virtual Box is a lot quicker than Xampp on Windows in my experience
answered 2 days ago
RDDWHRDDWH
62
62
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2fmagento.stackexchange.com%2fquestions%2f231412%2fbest-practice-for-local-development%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