Bazaar, the extension marketplace

clarkwinkelmann

The extension needs to access flagrow.io over HTTPS. The certificate is from Let's encrypt.

EvelinaAdamovi Maybe you need to update your root certificates for it to be recognized. What is your OS?

EvelinaAdamovi

luceos when eneblinh Bazaar.

clarkwinkelmann Windows 10. You think I need to install SSL on Xampp?

luceos

EvelinaAdamovi according to our devops (thanks Lars ? ):

there are no root certificates compiled in the windows binaries of PHP
just needs to set http://php.net/manual/en/curl.configuration.php#ini.curl.cainfo to point to a download of cacert.pem: https://curl.haxx.se/docs/caextract.html

This might be a bit hard to do by yourself as Guzzle is integrated into Bazaar. If your hosting environment does not have the appropriate (generally available) intermediate certificates we cannot be of any assistance ?

SierraKiloGulf

luceos
How might one do such a thing? I have 6 different forums I am managing and this ext would make it so much easier to manage them all. I am running apache on a home server, pretty positive I have SSL setup correctly but I am getting the same issue as this.

[deleted]

[deleted] clarkwinkelmann basically what happens, when you click on install.... it shows you the processing indication .... then as soon as the page auto refreshes to return you to the bazaar extensions list, you can see that the extension didn't get installed.... in pc the same happens but the extension does get installed

There are no errors whatsoever

@luceos can you have a look ^ this is a bug on mobile devices

jordanjay29

[deleted] flagrow/bazaar25

Confirmed and reported.

luceos

[deleted] error handling is currently quite bad in Bazaar. What happens is that any request that takes a bit longer is causing a timeout on the ajax call. I've currently catched this to refresh the page, because in most situations (during my tests on desktop) the installation succeeded. I now understand we have to do a bit more magic to make this work, I'm not sure yet how because Flarum does not yet support background queues.

I'll keep you posted, feel free to follow the issue on Github. Also we might have something in store for you that helps you manage your 9 installs ?

[deleted]

jordanjay29 awesome! Thank you so much ?

[deleted]

luceos thank you for your reply!

luceos Also we might have something in store for you that helps you manage your 9 installs ?

Oooo ..... #teaser ?

wignu

[deleted] luceos thank you for your reply!

luceos Also we might have something in store for you that helps you manage your 9 installs ?

Oooo ..... #teaser ?

They're going to find 8 and delete them ?

[deleted]

wignu haha what about the 1 that's left? ??

luceos

I've tagged 0.1.0-beta.4 today which includes:

Preventing caching of the extensions from our API when debug is on.
IT translation for the previous version.
The Flagrow.io dashboard.

The flagrow.io dashboard

When you've updated your Bazaar version to 0.1.0-beta.4+, you will notice the "connect" button on the Bazaar page allowing you to connect this Flarum installation to Flagrow.io. Once you've gone through the process of signing up and connecting, you will get access to a dashboard on our Flagrow app with all your connected Flarum installations, including their details in one place.

This is the first release and we will be heavily investing into additional functionality for Bazaar and your connected Flarum installation. For instance we're already able to allow favouriting of extensions in our backend, we will make this functionality available within connected Bazaars too asap!

Feel free to leave your feedback here. Please try to consolidate your issues on our github issue tracker.

[deleted]

luceos wowowow is this what you teased me about?

luceos

Small disclaimer (for those of you worried about connecting Bazaar to our app) until we've added an official one on our website:

The process of connecting your Flarum installation to Flagrow is completely secured, Flagrow.io uses a SSL certificate and the requests are made using the secure oauth2 principles.
We do need some information (like the version) about your Flarum installation and the Bazaar extension you installed. In addition we might gather some statistics about the extensions you managed through Bazaar at some point. All information you share with us through the extension and through Flagrow.io will remain private to you and us. We will never share this information, but will use it to provide useful features in the future.
You are free to have your account and related data on our app deleted at all times. Feel free to file a request through any communication channel (official channels coming soon).
Your authentication via our app is secured with SSL. In addition we will add two factor authentication in the nearby future.
Even if flagrow.io is down, your Flarum forum will continue to work, even though the Bazaar panel in your admin might not.

If you have any thoughts and ideas, eg about how we can improve our security and privacy, feel free to get in touch!

luceos

I noticed Flagrow.io had its mail configuration set up incorrectly.

Resetting passwords and registrations might have failed. If so please try again.

AngelAvila

Hello there! I've been noticing that when I install an Extension with Bazaar, many files gets overwritten which is cool, to avoid future issues.

But with the case of the oauth2-facebook extension with the most known issue regarding the

            $fields[] = 'bio';

line which breaks the extension completely appearing everytime I install a new extension with Bazaar, it gets a bit annoying.

Is there anything I could do to avoid this?

In advance thank you so much!

clarkwinkelmann

AngelAvila thanks for the feedback !

At the moment the extension always creates a new vendor folder with the new dependencies, and if everything went all right, swap the folders.

So this means any manual edit in the vendor folder will be lost if you do any action with Bazaar ?

This should not cause issue because we explicitly discourage editing core files.

I know the Facebook issue is a pain, it should really be fixed upstream...

I'll relay the issue to the Flagrow team so we can decide how to handle it.

luceos

[deleted] Yes ?

luceos

Tagged 0.1.0-beta.5

Dutch, Portuguese (thanks @1337god) and Spanish (thanks @AngelAvila ) language.
Allow favoriting extensions, only if you've connected your Bazaar.
Readme added.
Implemented, but disabled, code to allow registering our own satis into the composer.json for private packages.
Complete rewrite of the frontend, it no longer refreshes the whole page when doing actions on extensions.

The above was necessary in order to move forward with new features we are thinking about. If you'd like to have a say about our roadmap, make sure to become Councillor on Patreon.

existo

Today we made a small change to the bazaar back-end in our efforts to provide you with the best experience possible. By adding a caching layer for the images of Bazaar including http/2 support we are able to provide an even faster loading time when visiting the Bazaar page.

How did we do this? (For the technical people who are interested)
We configured a Nginx reverse proxy with caching enabled. This reverse proxy serves only static files on a separate subdomain. By enabling http/2 support, any modern browser will be able to benefit from multiplexing over a single connection to our image cache, something that was not possible with http 1.1. By doing so all images can be loaded simultaneously over this one single connection giving a huge performance boost compared to http 1.1.

I hope you will enjoy this small change we made. Any feedback is welcome as well.

Kyrne

existo would love to see statistics

« Previous Page Next Page »