“We saw an opportunity to build new tools into Local that pivot away from focusing on Flywheel customers and towards solving common WordPress developer pain-points,” Local product manager Jack Sellwood said. This major update focuses on pre-launch features that allow developers to check links, optimize images, share a live link, and make changes with live reload. The first version of Local Pro, launched in July 2019, was heavily geared towards Flywheel customers, but the tool has gradually evolved to be more host-agnostic. No issues with it working that way.Flywheel has relaunched Local Pro, the commercial upgrade for its free local WordPress development product. I’m installing it on a separate VM to keep it ringfenced away from our other apps. Just a word of friendly advice backed by real-world experience. So, all is not lost, but please take this as a mantra - if devs can’t use it, your users have no chance and they will flock to the next alternative. The end result will be lack of user confidence and bad press for your otherwise excellent piece of software (which has a lovely UI too). I totally agree with you here and that’s precisely what I’m trying to point out - if issues with your install have developers running around in circles (note: I have 20+ years IT experience in investments banking in City of London - hardly a hobbyist when when it comes to technology) - anyway, if it has developers confused, your users don’t have a hope in hell of figuring out how to “fix” things - which they shouldn’t have to in the first place. Just want to clarify what I meant about the last point where you mention that Flywheel is used by a much wider community than developers. Thanks - I’m glad you took the feedback in the spirit it was delivered and minus the (understandable!) angst that goes with having to install and reinstall something that really should be seamless. Good luck with rolling this out to paying clients Sorry for the harsh feedback, but do take it as constructive. We, as devs, use these tools all the time - the “correct” way, I add.Īll the hallmarks of an outsourced project with little communication and apparently no testing. Whether it’s docker or any other container or explanation is meaningless. and then failing to get even its own install right. It becomes poor practice on your dev’s part when the Virtualbox installation is forced on the machine, with no regard for versioning etc. Virtualbox is a breeze to install and most, if not all users can deal with it. – If virtualbox is detected on the host & if the version is less than what flywheel needs, give user option to upgrade or select cancel, else if it does not exist, install virtualbox.Įven a simple prerequisites note would do the job. No seasoned developer would make such a grave mistake over a simple nested if/then/else clause or similar approach required at the start of the installation: This is extremely, extremely poor coding. The version that fw tries to install is not the current version, therefore, it messes up the virtualbox install and the existing vms in the process before failing to install itself. Turns out that the flywheel install was doing its own installation of virtualbox despite there being an existing installation on the host machine. Not only would the flywheel install hang, it would randomly kill the virtualbox process, leaving each of our existing vms in a hung state and needing recovery. The worst part is that each time, the failed install corrupted my existing install of virtualbox which runs multiple VMs which we (being a small company) use in production for our dns, gateway and other infrastructure stuff. Hi all, just thought I’d chip in - I tried the flywheel install many times as well with the same issues above. Personally I am not looking forward to it, because I use an old Mac Pro at home and that cant run the docker without virtualbox. In the fullness of time, there is a version of docker that does not require the entirety of virtualbox, and you may look forward this, but in the meantime, your options are Flywheel with virtualbox or perhaps some other tool like MAMP or XAMPPS. I know that virtualbox looks to be a bit resource hungry, but looking at my imac, it is actually using a grand total of 26.5Mb of memory while idle, and 3.5% of one of my many cpus. This is the main feature of flywheel, which uses docker, and virtualbox is the tool that docker uses to provide it. Then after Virtualbox was removed, Flywheel felt the pain, and attempted to re-install it.įlywheel runs the websites inside a virtual Linux computer, this provides isolation and a running environment that is as close to the server environment as is possible to get. The first time you installed Flywheel, you already had VirtualBox installed, so it did not need to perform that install.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |