![]() ![]() As far as further Magento specifics go, please feel free to ask, but I don't know a whole lot about it, so you may be better off seeking advice from seasoned Magento users (e.g. Hopefully that gives you a bit more background. I don't know anything about it, but I suggest you give that a go for migrating data from older v1.x Magento sites. Perhaps you might have better luck following those instructions?įWIW if you check the appliance page that includes links to the "official" Magento v1.x to 2.x migration guide and they note that there is a data migration tool. Upgrading via composer), the proper instructions for updating (as per the way we installed) is instead this page. v15.0).Īccording to that doc page you linked to (i.e. If you wish to see how it was installed, please check the build code (conf script is likely the logical starting point) at the relevant version tag (e.g. If you are using TurnKey v14.2 or later appliance, then we download the code via a shallow git clone, then install with Composer. Good luck with it all and please feel free to share any more thoughts you have. We really appreciate it and I hope to at least include documentation for usage of composer and note the Magento admin url. Whether we'd move to pre-integrate it with other appliances, I'm not sure. In the near future, we'll likely provide a standalone Redis server. I'm sure it provides advantages and we probably should consider including it with some apps. Redis I'm not so familiar with personally. The interesting thing about that is that it caches the static content, so likely would boost Apache performance much more that Nginx, although again real world results would depend on your specific use case. Your suggestion for Varnish is a good one. So to be able to use Apache as a common component with decent default config reduces our maintenance overheads. htaccess files, we do have PHP apps in the library which do. Whilst that doesn't necessarily have any direct impact for Magento or other projects which don't rely on. It also has fantastic documentation and a Webmin module that makes it quite newb friendly. Most of them are packaged for Debian, so we can leverage the auto security updates. ![]() Now that PHP7 has implemented many of the improvements that PHP-FPM provided, you should find that Apache using mod_php should actually be able to process PHP faster! Admittedly, any advantage in PHP processing is often lost several times over because of the resource overhead of mod_php being loading into memory when serving static content, so in the real world, it's rare to see significant improvement, but it's worth mentioning.Īpache also has a range of module and plugins which makes it very flexible. So for a PHP web app such as Magento you have to run a separate PHP processor (usually PHP-FPM). First thing worth noting is that it's actually only better at serving static content, it actually can't serve dynamic content. I quite like Nginx and I know that it is hugely popular, but we do have reasons why we don't use it by default. Then you're running as the user: www-data! :) At the very least we should clearly document how to use the Even though www-data user does not have a shell by default, that doesn't mean that you can't run as that user with a shell! So to open a shell session as the www-data user, try this: su -c /bin/sh www-data su - www-data -c /bin/sh As far as I understood it, the biggest issue with using composer as the root user is that it will affect the file permissions (stuff will be owned by root, rather than However, a quick read here actually alerted me to the real potential security issues! I was aware that there had been noises about security concerns, but I was under the impression that that was the usual "Ubuntu user" type noise about "shouldn't ever run as root" and the only real world issue was permissions. I've opened a new issue.Ĭomposer running as root: Thank you for raising this. Regardless, we shoudl document it for now. If it's on install, then perhaps we should ideally be regenerating it on firstboot (and display it on the confconsole). My bad! Also, I'm not sure if that's setup on install, or on launch. I recall noticing that the admin URL used a random string when I did testing, but I didn't note it at the time. I'll try to respond to your points in order: So "getting it right" by everyone's standards, is near impossible. Having said that, we have a huge array of users with different desires, needs and preferences. ![]() We really appreciate and always try to take stuff on board. Thanks for your feedback on our Magento appliance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |