Bazaar, the extension marketplace

clarkwinkelmann

XxPoNaGeXx are you talking about the fact Bazaar prevents access to other parts of the Admin UI while loading ? That one's related to flagrow/bazaar107 ?

The loading screen is Bazaar getting the updated list of extensions from flagrow.io. There's more and more extensions so it's time consuming.

We've got plans to redesign the homepage and improve loading speed.

XxPoNaGeXx

clarkwinkelmann No. I'm talking about how when I'm loading the marketplace up the front end of the forum doesn't display any errors just the little loading animation for about 5 minutes

clarkwinkelmann

XxPoNaGeXx oh yes this can happen. Depends how many processes your webserver can handle at once. If a single php script can run at a time, any Bazaar task will eat it up for several seconds/minutes and prevent anything else from running.

Cron processing in the next version should help with that.

luceos

We're moving Flagrow.io to its own server (away from our incubation server). We need the dedicated resources to optimise the indexing of flarum extensions in preparation of the premium extensions.

This also might have an effect on the availability of extensions listed in Bazaar. Bazaar might temporarily misbehave while we get ready for the move.

The migration is taking place in the coming hours. If after 12 hours from now you still experience any problems with either flagrow.io or bazaar; please either respond here or post an issue on our github repository.

Thanks for your patience.

luceos

Tech talk section:

Yesterday I lowered the TTL of our flagrow.io domain in preparation of the migration. So just now I put the old (laravel) installation in maintenance mode, moved the last database export using scp to the new server (50+mbps), imported it, ran the last checks, acquired a let's encrypt certificate.

The move seems to be working properly, the homepage is snappy, instead of running package indexing fully in a cronjob (scheduled task) part of it already has been segregated into queue jobs monitored using Horizon.

Previously we would use circleci + ansible to deploy our website, for ease of use and team accessibility I've changed to circleci + forge. The new server is hosted on digital ocean for now, the next stage when we need to scale up again would be targeting full cloud Google Kubernetes Engine.

Thanks for your patience, if anything seems to misbehave, please let me know ?

luceos

Flagrow.io is undergoing some maintenance. Your bazaar might temporarily not work.

Our apologies for this unannounced work.

luceos

Today has seen the release of a new version of flagrow.io. This new version is another step towards our grand plan ? of getting Bazaar, premium extensions and additional added features available to the Flarum community.

Much has changed since the beginning of this year. The original team collaborating under a legal entity slowly dissolved with just me and @clarkwinkelmann remaining ending in us folding the cooperative called Gravure. Even though that was a sad moment, we remained motivated to finish what we started. We are actively targeting to release everything we're working on as soon as Flarum beta 8 lands, including a few premium extensions of our own, an improved Bazaar and a centralised dashboard for keeping track of your Flarum installations!

If you encounter any issues inside Bazaar or on Flagrow.io, feel free to let us know.

Make sure to check out our new extended search allowing you to filter extensions by their compatibility with Flarum: https://flagrow.io/extensions

luceos

What would Flagrow be if there wouldn't be more information on the technical side of this update ?

A full rewrite of the frontend code, moving away from Laravel blade files which had inline Vue templates. Now the complete site is one Vue single page application.
- The benefit of this is that we can reduce loading times on every following page, in addition measures have been taken to offload loading only when needed. A great example of this is when you hit the advanced search page for the first time (or clear local storage) and select a Flarum version, this list will only be seeded when you need it. But once you did that data is reused on the complete site by using vuex.
- We're now mimicking Collections and Models inside Vue using ES6 the same way Laravel does. This allows for one unified way of working with the app; it's easier to understand and accelerates development speed.
Upgraded to font awesome 5 (pro), the default icons for Flarum beta 8. That's why currently icons aren't shown.
Upgraded to the latest Laravel 5.6.
Many layout and UX issues have been taken care of. Our plans are to do a complete overhaul of a few pages in the near future.

luceos

Some people might have ran into issues with Bazaar, eg just a few minutes ago someone tried connecting Bazaar to Flagrow.io which failed. I'm resolving issues as soon as the errors come in; we use Sentry on flagrow.io for that, sadly we can't really track errors on Bazaar so please do report anything you find as an issue on Github or here.

Jenxi

luceos I was having issues yesterday, not sure if that was me. However, it's not a Bazaar issue. It's due to reflar/polls not uninstalling properly. So I wasn't able to enable or uninstall the extension. Bazaar just threw an error and asked to refresh or submit a report. The issue has since been resolved by going into phpmyadmin to remove the columns that were there. That said, there should be a way for Bazaar to say what was causing the error instead of having to be in debug mode to see the error message.

It could well be someone else who triggered that but this is just my heads up.

luceos

Jenxi have you checked the tasks tab inside the admin Bazaar page? It should show the raw response from composer. If you have an actual error inside Bazaar I'd appreciate a report so I can investigate ? thanks for getting back to me about this ?

Jenxi

luceos Which tab is it?

Jenxi

luceos I found it, the last action was 5 days ago, so I don't think it's an error in Bazaar.

luceos

Jenxi can you post me the error you found or your flarum.log in storage/logs/flarum.log please do so privately (on discord?)

Jenxi

luceos Alright I'll ping you on Discord.

luceos

Having taken a temporary leave on full active Flarum core development to take the last hurdle with paid extensions has paid off. September and most of this month I have battled to go over all the steps required for the workflow to succeed, eg:

As a developer;
- sign up as a user
- receive an invitation to create a team
- land on a onboarding page to:
- set up your stripe connection
- connect your privately owned git repositories
- configure repositories to be a premium package by selecting a team and a pricing tier
- ensure premium packages show up on the flagrow.io search
- confirm you can subscribe and unsubscribe on flagrow.io
As a user;
- install Bazaar
- connect Bazaar to flagrow.io; requiring you to sign up
- ensure you see a premium extension
- click to subscribe to extension

There are still a few kinks in the cable. But so far it's looking good. In the meantime the initial premium tiers have also been decided on:

Kindling Premium : $ 5 per month
Spark Premium : $ 10 per month
Ember Premium: $ 15 per month

Subscribing to an extension allows you to install and update it. Once you cancel your subscription your installed extension will still be usable on Flarum forums you installed them to, but you can no longer upgrade or install them.

Premium extensions can be expected soon after the release of Flarum 0.1.0-beta.8.

Informational links (still under development):

Shahiem

luceos I'm really excited for this. 😮 What's the difference between the premium tiers?
(except the price)

luceos

Shahiem the price 🙈

Developers can decide with us for what tier their extensions should be sold as.

tobort

Hi Flagrow dudes,
I've just got Flarum up and running, the base install seems fine. When I install Bazaar (or any Flagrow extension, haven't tried non-flagrow exts), this is what I'm seeing on the admin end. I didn't know how to search to see if someone else had this issue. Does this look familiar? Any ideas?

Kyrne

tobort clear your cache by typing php Flarum cache clear then clear your browser cache. Alternatively, you can install reflar/uncache and you'll never have to do this again

tobort

Kyrne Weirdly, I had tried that last night with no luck - today I restarted apache & it resolved. I'll install uncache and hopefully that'll make this a thing of the past. Thanks 🙂

« Previous Page Next Page »