Hello, we're looking for help to upgrade Avo 2 to Avo 3 at RubyGems.org. I was able to use auto-upgrade tool and few manual changes to get at least app boot and running, but there is still a lot of problems and tests failing. The biggest problem I do see is multiple gems for Avo 3 since RubyGems.org is app with open source code and we have no way to add other than public gems into Gemfile. Is there any suggestion for this? We would like to avoid kind of conditional gem deployment. Currently I see a lot of errors like following one. Are those caused by missing

avo-*

private gem? Is Avo 3 still friendly to open apps as Avo 2 was?

AbstractController::ActionNotFound: The action 'index' could not be found for Avo::SearchController

Thread automatically created by retro♐ in #740893011994738751

Hey @silly-lion-46554. I started a conversation with Sam about that. It’s a bit tricky with open source but I have a few ideas on how to get and use the private repos safely as an open source repo

There was some private API used, that's clearly mistake on our side and should be removed. But what about the missing parts in public gem? Is the search index action one of them?

I told Sam about this, one of our main concerns is not to have the paid gems leaked in OSS repos. We’ve had quite a few enounters with bad actors in Avo 2 and we’d like to avoid that

Sam has sent me here to continue discussion. 🙂

Hahah

I'm here just to find out what to do, since Avo 2 currently breaks Rails 7.2 upgrade for us so we have like 3 options: - onboard Avo 3 somehow - leave Avo at all - try to fix Avo 2 with newer deps and buy some time to take a look later

The global search feature is paid. I’m not sure why you can still see the global search field (where I presume the error comes from)

not really

I’m trying to asses all scenarios

7.2 wasn't even released yet

Yeah. Got it

I'm happy to check Avo 2 and update on my own.

The happy path for us and I guess for you too is to get you on Avo 3, but this requires some work on iur end

You have all time you need. We're not in rush for now. I'm just wondering what's the plan here.

The result would be that anyone can run bundle install and work on the public side of rubygems and the community side of Avo. If that env has the paid gems token, they will be able to install the paid gems too and work on the whole thing

We would ship “dummy” versions of the paid gems from our gemserver

That would be awesome. Sam tried originally to detect if paid gem is loaded using like

Gem.loaded_specs["avo-pro"]

...

Worst case scenario, only the prople with the Avo credentials will be ablt to work within Avo

We would like to keep developers able to keep their development luxury, like running full specs for app locally.

I understand

And no worries, if there is no way to achieve this, we can manage somehow.

Yup. Got it! I know what you’re aiming for

awesome!

Not sure! I need to fix the broken tests, and then make sure my check that we do indeed have pro is working (because not having pro silently disregards the authorization…)

hmm, we'd be open to add a safeguard for that