Bazaar, the extension marketplace

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

Legoman99573

This is badass. I like what you did with it. This should be a built in feature

luceos

I've updated the OP to include a requirement after installation. Bazaar needs to be able to read and write a few files and directories:

Make sure that the following directories and files are writable by the web user:

composer.json
composer.lock
vendor/

@bane thanks for helping figure this out ?

Legoman99573

BTW

I would disclaim it wont install all extensions as some generate errors and some will install fine. Other than that, its a good extension still.

Plus one more question. Is there a way to show the extension has an update available?

bane

Legoman99573
Check #Post5151-72

luceos

Legoman99573 both of these are on the roadmap. Blocking non-functional extensions is the topmost priority, but I'm currently a bit tied up with a (soon ™ to be released) update for flagrow/upload ?

Legoman99573

luceos Not in a rush. Take as much time as you need as i can see which ones dont work ?

[deleted]

@luceos I just got time to test out flagrow.io and it's really cool.... but won't it allow us to install/remove/update extensions remotely in the future? Since that's what I thought it does until I tried it

luceos

[deleted] yes those features are on the roadmap. We also plan to do unattended auto updates and sending email notifications about the health of your forums.

[deleted]

luceos that's amazing!!!

luceos

0.1.0 released
- Moved our loader modal below the error popup.
- Added a contributing document.

Dropped the beta so installation will be less bothersome.

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.

luceos

SierraKiloGulf our certificates are provided by let's encrypt this might be the culprit. I'm not sure updating your certificate roots should be possible on any OS, what OS are you on?

Feel free to join our discord channel #flagrow-support so we can resolve faster.

SierraKiloGulf

luceos
Waiting for verification email and then I'll hit you up on Discord if I can ever figure out how lol
My sys runs W10, Apache 2.4, php7.1

luceos

? version 0.1.1 released, with the ability to update an extension!

Also:

Huge refactoring. Extension manager logic moved into the repository.
Extensions with available updates are now marked "outdated".
Allowing updating of single extensions when outdated.
Flush cache, including manifest (not yet fixed in core), during (de-)installation and updating of packages.
Fixed tooltips overlapping for extension title and badges.
Gave badges a color based on their state indication.
Not showing "installable" badge when extension enabled.
Refactored tests namespacing to adhere to psr standards.
Removed console.log debugging from xhr calls results.
Now showing latest version or current version on extension card.

In order to update:

composer update flagrow/bazaar
php flarum cache:clear
rm assets/rev-manifest.json

Two things I'd like to point out:

If using nginx, you might want to increase the fastcgi_read_timeout to at least 300s, this will prevent Nginx from throwing a 405 error which make it seem that installation, updating, removing extensions does not work, albeit the php process might still have succeeded.
We really need quite a bit of memory ?. To ensure Bazaar has sufficient memory either set your memory_limit in the php.ini to 1024M or make sure we're allowed to use ini_set to override the memory_limit.
After updating an extension we have to reload the page. We cannot modify the installation state of an extension within Flarum during runtime.

luceos

luceos ps if you want to test out that marking extension as outdated works, just move an extension back manually using composer, eg:

composer require flarum/flarum-ext-auth-facebook:0.1.0.beta.3

Then refresh the bazaar page ?

I recommend using an extension for this that you already installed but have NOT enabled!

tanzaho

Hi,
This is a very naive question, but I'm getting started with Flarum. I've tried to install Bazaar on a fresh 0.1.0-beta install with the French language package, and:

After install, when I enabled the extension I got an error message (white page, php error smth). I didn't write it down because a refresh fixed it.
Now the extension is enabled but I can't "read it". Is it because there is no French translation and there is no default fallback to use the English version? Here is what I see :

If I turn my forum to English, I can see correctly labels... but I can't keep the forum in English for my future users.

luceos

tanzaho I was assuming it would fallback to English. If you're up to provide me the translated strings I'll gladly add them:

https://github.com/flagrow/bazaar/blob/master/locale/en.yml

tanzaho

luceos That's the behavior I was expecting too. I didn't check yet if it was a Flarum bug on my config, or just for Flagrow extensions. I'll try to come up with some translations when I'll have some spare time.

« Previous Page Next Page »