Giter Site home page Giter Site logo

site-market-bolt-cm's Introduction

Bolt Extensions Market Place Repository

Theme

Theme is provided by the bolt/marketplace-theme.

Running Scheduled Jobs

Dump package repository JSON from database

./app/nut package:dump

Rebuild JSON data for all packages:

./app/nut package:build

Rebuild a single package's JSON data

./app/nut package:build author/pachage

Flushing the hook generated update queue:

./app/nut package:queue

Running extension tests

./app/nut package:extension-tester [--wait=n] [--protocol=http] [--protocol=https] [--private-key=~/.ssh/id_rsa]

site-market-bolt-cm's People

Contributors

bobdenotter avatar gwendolenlynch avatar mikescops avatar phillippohlandt avatar rossriley avatar royallthefourth avatar sahassar avatar silentworks avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

site-market-bolt-cm's Issues

[RFC] Show provided widgets

Hey,

now where we can include widget locations in themes, I would find it very useful when the extension store could list them.

My idea is to add that to the extra section in the composer.json. Something like

"extra": {
        "bolt-widgets": [
            "aside_top",
            "aside_bottom",
            "footer"
        ]
    }

or with a description

"extra": {
        "bolt-widgets": [
            {
                "name": "aside_top",
                "description": "Right before the latest entry list"
            },
            {
                "name": "aside_bottom",
                "description": "Right after the subscription form"
            },
            {
                "name": "footer",
                "description": "At the top of the footer"
            },
        ]
    }

Personally, I prefer the one with the description, because then it's easier for the user and can act like a little documentation. Also, more metadata is always better :)

I would take care of the implementation in the extension store then.

Including Readme on the extension/theme page

Hey,

most extensions/themes have just one or two sentences as description but a good Readme with all instructions you need.
Maybe we can include it on the extension/theme page so a user can stay on that page and don't have to move to github?

Typo

typo

Should be

You must be logged in to star packages

Can´t register: PODException

Hi,

i hit "Sign in with GitHub", gave all perms & added then username, mail & password. After Submit i got this Error:

bildschirmfoto 2018-01-31 um 19 46 27

Add Lightbox or FancyBox when clicking on Screenshots

It would be awesome if there was a way to click screenshots and display a bigger image of the screenshot on the page. In the current design you are stuck with the thumbnails, which are great, but THEY ARE SO BLOOOOOOOOOODY SMALL!!! MY EYES!

Github login fails

Hi!

I tried to login with github to the extension site, but got this error:

screen2

Am I doing something wrong? :)

Profile url mapping issue

When I am logged into the backend, the "profile" link which should lead the to profile edit page of the bolt user links to /profile which is the profile of the frontend user.

Seems to be some route name collisions.

[RFC] Package Update Notifications (Subscription System)

Hey,

I think I a nice feature would be when a user can subscribe to a package to get a notification email when a new version of the package becomes available.
E-Mail notifications because it's the easiest right now. We could also plan a real notification system inside the Bolt store for the future, though.

Timeout on IPv6 https://market.bolt.cm/satis/packages.json

Hi,

I am not able to install extensions on my local testing machine.

What is working is:

  • search for a extension
  • select a version of the extension (its possible to see the latest versions)

What is not working:

  • the next step "installation is preparing ....." stops after long waiting with:

    Composer Error
    The "https://market.bolt.cm/satis/packages.json" file could not be downloaded: failed to open stream: Operation timed out
    

I tried it with nut server:run and php -S localhost:8000, both didn't work, the second gave some logging:

[Mon Feb 26 01:03:35 2018] ::1:63383 [200]: /bolt/extensions/installInfo?package=bobdenotter/passwordprotect
[Mon Feb 26 01:05:28 2018] ::1:63420 [200]: /bolt/extensions/installInfo?package=bolt/robots
[Mon Feb 26 01:09:38 2018] ::1:63428 [500]: /bolt/extensions/install?package=bolt%2Frobots&version=v1.0.1

Internal Server Error 500 in /bolt/extensions/install.

So I tried to download the file by hand:

~/temp % wget "https://market.bolt.cm/satis/packages.json"
--2018-02-26 00:24:43--  https://market.bolt.cm/satis/packages.json
Resolving market.bolt.cm (market.bolt.cm)... 2a03:b0c0:0:1010::20f:5001, 82.196.12.59
Connecting to market.bolt.cm (market.bolt.cm)|2a03:b0c0:0:1010::20f:5001|:443... failed: Operation timed out.
Connecting to market.bolt.cm (market.bolt.cm)|82.196.12.59|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 192 [application/json]
Saving to: 'packages.json'

packages.json                           100%[============================================================================>]     192  --.-KB/s    in 0s

2018-02-26 00:26:00 (6.10 MB/s) - 'packages.json' saved [192/192]

~/temp % more packages.json
{
    "packages": [],
    "includes": {
        "include/all$111d59491eb841b6744af5b48d2ddfbdc4e9d7c1.json": {
            "sha1": "111d59491eb841b6744af5b48d2ddfbdc4e9d7c1"
        }
    }
}
~/temp %

It seems my box (macOS 10.13.3) seems to prefer the IPv6 -IP- adress of the server - which times out.
wget is clever enough to use the IPv4 adress for the next try, the Bolt Backend unfortunately just stops.

On another box (Cent OS, other internet-provider) the installation of extensions through the Bolt-Backend works as expected - there the setup seems to prefer the IPv4 adress ("tested" with the wget approach shown above).


Maybe this is just a misconfiguration of the DNS-Server? It seems the IPv6 Adress (2a03:b0c0:0:1010::20f:5001) points to bolt.cm, not market.bolt.cm ??


Or maybe the configuration of IPv6 in cooperation with HTTPS wasn't done correctly.
I had contact to a similar problem some time ago - but unfortunately I have no detailed infos what exactly had to be changed.

[FEATURE] Built-in extension documentation

The idea is to provide real documentation pages for extensions. That means they can split it over several pages and don't need to put everything in the readme.

For simplicity, the documentation markdown files will live inside the git repository so everyone can contribute changes and we don't have to build a whole management system :)

Documentation versioning could be used via git itself but that makes later changes a bit difficult so I suggest a filesystem based versioning system.

Repository Structure

├── README.md
├── composer.json
├── config
├── docs
│   └── v1.0
│       ├── contribution.md
│       ├── extend.md
│       ├── installation.md
│       ├── introduction.md
│       ├── menu.yml
│       └── usage.md
├── phpunit.xml.dist
├── src
├── templates
├── tests
└── web

You can see, the git repository contains a docs folder. Inside this folder is one folder for each major/minor (depending on the needs) version of the extension.
The version folder contains a menu.yml file which defines the order and names of the specific documentation pages.

menu.yml

- title: Introduction
  file: introduction.md
- title: Installation
  file: installation.md
- title: Usage
  file: usage.md
- title: Extend the Extension Functionality
  file: extend.md
- title: Contribution
  file: contribution.md

The menu.yml is just a simple definition file for the navigation.

Note: The files above are just as an example. It's completely up to the extension developer to define the documentation structure for his extension.

Implementation inside the Store

I would suggest the following URL structure for a documentation page:
https://extensions.bolt.cm/view/ohlandt/user-profiles/docs/v1/introduction
So it almost mimics the file structure inside the repository, except that we removed the .md for the URL.

It will also make sense to save the whole documentation somewhere so we don't have to pull it "live" from Github. It would be updated on every update (manually or via hook) in the store.


What I described above is my idea of an easy implementation. But I am also open to suggestions and other ideas :)

Could not add star anymore

When I am logged, I click on star button on an extension page, and get Your have already starred this package error message, even if I have not this extension on https://extensions.bolt.cm/profile/starred page. Seems to act like that when at least one member has starred the extension.

[RFC] Extension of the Week

As already noted by @GawainLynch in #54, there could be an "Extension of the Week" competition.

I actually really like the idea because it promotes some community activity (I hope).

That's how it should work in my mind:

  1. Someone picks X (random?) extensions (on a Monday)
  2. People can vote for 1 of these extensions* (until Sunday)
  3. The extension with the most votes is the Extension of the Week until the people voted for the next extension

*We can also give everyone 3 points and then they can give all 3 points to one extension or 2 to A and 1 to B, etc.

Why "X extensions" and not all?
Simply because to avoid that people always vote for the same extension.

How do we track votes?
I would prefer that we require an account in the store. This can also lead to more engagement in the store itself (starring extensions, etc).

Comments very appreciated.

Bolt.cm Market Extension URL from Gitlab

The URL of my extension repo is https://gitlab.com/Danatur/bolt-extension-twitch/, so the market links the extension icon to https://gitlab.com/Danatur/bolt-extension-twitch/master/icon-twitch-extension.png

However, on Gitlab you can only access the extension icon under https://gitlab.com/Danatur/bolt-extension-twitch/raw/master/icon-twitch-extension.png

It would be nice to have a fix for that.

Latest version isn't updated anymore

Hey,

after some people have upgraded their themes and released new versions, the extension store still shows the old ones, even on themes which were updated in the extension store. Here are some examples:

http://extensions.bolt.cm/view/c033c792-7a75-11e5-86fe-396a68cabe59
http://extensions.bolt.cm/view/029aac22-6d15-11e4-866c-43d66b93a270

This also effects the json api I use for boltthem.es.

There is only 1 theme which shows the correct version:
http://extensions.bolt.cm/view/f6f3ea5a-7a6a-11e5-86fe-396a68cabe59

[RFC] Using an extra md file for the description

It would be nice to have the ability to use i.e. a description.md for the description of the extension.
This way it is easy to add some simple markup to the description part like links etc.
Also a change there will be a bit more info, so you don't need to go to the git website for additional info.

Copy to clipboard not working

extension-extras.js?10c575006f:8 Uncaught ReferenceError: ZeroClipboard is not defined
at HTMLDocument. (extension-extras.js?10c575006f:8)
at i (jquery.min.js:2)
at Object.add [as done] (jquery.min.js:2)
at n.fn.init.n.fn.ready (jquery.min.js:2)
at extension-extras.js?10c575006f:1

Need better wording / grammar for starring a package

screenshot from 2018-08-19 18-01-59

The message currently says "Your have starred this package".

Consider perhaps "Your neighbors have starred this package", or even "Your local politicians have starred this package".

;)

Pull request coming.

[RFC] Filter extensions by favorites

On page https://extensions.bolt.cm/, when I'm logged in, I could mark my favorites extensions. But when I'm logged in, I didn't find any page with all my favorites extensions. It would be nice to have such a page. (Try url like https://extensions.bolt.cm/star/list or https://extensions.bolt.cm/stars but get error pages).

Search buggy

When I search for user profiles I don't get any results. When I search for profiles I get my extension and the Members extension.

This also affects the extension search via the Bolt backend which is "not so nice".

Until Extensions website Final Release

Here you are a list of things i couldn't do on my local copy :

  • Add new fields in database such as icon, support links..
  • Handle incorrect repository URLs when submitting extensions ("show custom error message on invalid URL instead of FatalErrorException") -> see bolt/bolt#3987
  • Search system is a bit blind (try to type "gawain" and you get only 2 extensions 👍 )
  • Contact developers to update their extensions with the new fields
  • Handle the changelog and release (with and without GitHub) -> actually working on client side
  • Authors of extensions need a fix / a bit messy with the contributors (add gravatar support for them ?)
  • SEO fixes

You can assign tasks below. Dev public version will be publish on 19/08/2015.

Broken "Archive" pages?

Extensions live at links such as https://market.bolt.cm/view/soapbox/redirectsmanager.

But if you go up a level to what (I guess) would be the listing of that user https://market.bolt.cm/view/soapbox the page displays a number of errors.

image

[RFC] New homepage structure

I am a little bored of the current - always the same - store homepage. I think we should sit together and plan a new one. It doesn't have to be overly complex or in a new design, just another layout and a bit different content.

There is already the Featured Extension RFC from earlier today which can be included in the planning. I would also like to see some extension collections featured there.

To be honest, I don't have something special in mind, just the wish for something new, maybe more dynamic, which gives a bit of fresh air to the store homepage.

Any ideas?

[RFC] Featured Extension

I thnk it would be nice if we can feature (or let feature via cronjob and random picking) extensions on a daily basis. Right now the Store homepage doesn't change much and many extensions are never really seen by people. I already tried to solve that with my approach of defining extension collections but having a daily featured extension on the homepage would help a bit more I think.

Update button redirects to /bolt/login

When clicking the update button on the package list to force a update of a package I am redirected to the bolt login page. No package update seems to be done.

The requested url is https://market.bolt.cm/bolt/extensions/update?package=e1310b36-fc83-41b7-b0aa-569a34bcf040 and the response is a 302 Found with Location:/bolt/login.

Browser: Chrome 59.0.3071.86

Unable to create an account

While trying to setup an account you will be returned to the register view. All the fields are cleared and there is no kind of feedback like an error message.

Waiting for tests to run

Hi all,

This is probably completely the wrong place to post this, but I have no idea where else to put it, so apologies.

I have submitted an extension to the market place and clicked Run Tests, but it's been hanging on "Preparing Test Build" for 4 days now. Just wondering if I've done anything wrong, or if something your side has got stuck?

The extension is maxmumford/youtube-filter (1.0.1).

Thanks

[Tracker] Transition to "Marketplace"

Ok, I think the decision was already made mooooonths ago, so this is not an RFC but a tracker.

We already renamed this and related repositories, got the new wording on a few pages in the docs and use the "Marketplace" term day in and out, but we didn't actually made the real transition.

This are the steps that should be done in order to properly transition:

  • Put extensions.bolt.cm on market.bolt.cm
  • Make 301 redirects from extensions.bolt.cm to market.bolt.cm for backlinks and Bolt backend BC
  • Change heading on the marketplace application and look for other text sections to change
  • Check documentation for text sections and links to change
  • Change links on bolt.cm
  • Adjust bolt/bolt to point to the new URL for extension handling (3.2/3.3) (even if we have the redirect)
  • Moving the Disqus set up (Disqus was removed in PR bolt/marketplace-theme/pull/6)

That are the ones that pop up in my head, if you have additional tasks, feel free to add them.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.