Failed Readiness Check on GoDaddy due to Component Dependency

[mike_latzky]

So, some updates:

I appreciate all the help!

I've checked around and have investigated many hosting services. Since we're still in pre-pre-pre launch (really just investigating feasibility), I've gone with 3-month Business hosting at GoDaddy. 6gb RAM, and all the necessary resources needed to run Magento 2.32 CE.

The composer issue is still a problem, even with Manish's suggestion. I've tried stepping up through all versions of phpunit from 6.5 through 7 and still get composer fails. I'll post the output tomorrow or so to show.

I've still got to resolve the php, cron, etc fails, but hope to get some help to resolve those as I got help from GoDaddy support previously....

In short, 1 step closer, a few steps back, but plowing on...

[JLHC]

To be honest I'm a little puzzled with your insistence on continuing with GoDaddy and even went with a more expensive plan with them instead of considering a proper Magento optimized hosting provider who are very familiar with Magento, has the environment setup for it and will be able to provide assistance with Magento specific problems.

We don't have access to your server or your environment so all we can do is provide suggestions and assistance from afar.

You should not even face simple problems like this if you consider going with a provider which has their environment setup for Magento out of the box.

[mike_latzky]

As a novice to all of this, I admit to being swayed by what I hear when I speak to someone at a service I know. But I can also admit when I hear smarter voices on a forum built to support a particular app. I hadn't heard of Nexcess before, although I did call Magento directly and got a price which was beyond my sandbox budget.

If Nexcess can provide the kind of direct setup support, at a price of about $30/month for a few months of sandbox time, I'm all for that, and am still in time to cancel my commitment to GoDaddy by tomorrow morning. Can someone give me a spec I need to ask Nexcess for where they can provide me the kind of support for? At any rate, I'll call them, and the other 2 companies in the morning and ask them directly what they can provide and see what I can do to get a hosting service that has specific Magento experience.

I appreciate all the help and sticking with me! It's definitely not stubbornness on my part, it's stumbling through an unfamiliar wilderness!

[JLHC]

All 3 companies mentioned by @Robert Rand will be able to support Magento out of the box and as they specialize in Magento, will be able to provide support for Magento related issues. 

You should be fine with any of the plans they offer as you should be able to upgrade to a higher plan with them if your needs increases. 

[mike_latzky]

Advice taken and signed up at Nexcess - very nice people.

I appreciate everyone's help. I'll post more if there's still an issue they can't solve when I bring up the Magento instance there with their help, otherwise I'll mark the issue closed and post kudos.

Thanks again for advice and help. 

[mike_latzky]

After the Nexcess folks got me up and running within a matter of two hours, I managed to do a little exploring. The composer issue is still present, and I edited the composer.json to the ^7.00 version of phpunit recommended by Manish. 

The site is using PHP version 7.1.30, and Magento 2.3.2. And, of course, after initial install of Magento 2.3.2, I ran a composer update to ensure that all other modules were updated with the initial composer.json script which specified phpunit 6.5.0. I then edited that to phpunit 7.0, which produced the output captured in the screenshot below.

Unfortunately, it still left me with an irreconcilable install. I grabbed a screen shot. Hopefully, this will make sense for someone to recommend a fix?

[mike_latzky]

After wrestling with several issues for days, I got to a solution and passed the first stage of the Readiness Check. Here's what I got:

1. I moved to a hosting service that understands Magento. Thank you to all who persevered with my novice-ness and recommended (in this case) Nexcess - they have been amazing, patience, and knowledgeable.

2, It took changes to the composer.json. The support person made the following changes, similar to what Manish recommended, and some additional ones to get past other issues that came up, as it still barked about phpunit:mockobjects being abandoned. I'm sure there are other ways around this, and it would be good to hear of them, but this is the route he took and it worked.

3. And finally, it took bumping the session memory up to a huge 1400M from a usual recommended 756M in the .user.ini file. Once we got there, it passed.

I'd also like to add that within one hour of signing on to Nexcess, they had spun up a Magento instance that had cron set up, and had passed 4 of the 5 Readiness Check issues immediately, with only this final issue around the Component Dependency not passing. And their Tech Support person spent an incredible 3 hours working on everything. This in only a $25/month hosting plan, allowing me to have a playground to test a business idea. 

I wouldn't recommend being so cheap, nor trying to use what is obviously such a powerful system that is incredibly resource intensive on a platform with such relatively low power, but it does run ONLY for playground purposes. As I get familiar and prove out the business idea, it will clearly need to move into their Cloud platform to take advantage of all of the other technology that Magento offers. And eventually, from Community Edition, into Enterprise Edition, should the business idea prove success and warrant what that platform offers. 

In short, I'm starting to get hooked.

Thank you all for this starting help and I look forward to more.