Extension development using composer repositories path

luceos

DiegoPino

Within workbench you have another folder for your extension. The name of this folder doesn't matter as composer will scan each directory inside of workbench for a composer.json file and use the name attribute. For your own sanity it makes sense to name it something so you can identify it with. For instance the folder for byobu is named "messaging" on one of my machines ever since I started out, because I decided on the name after creating the folder. So yes <flarum docroot>/workbench/<extension name>/composer.json is what matters.
This can be caused by several things, check for the following;
- are you running the command inside the flarum docroot?
- is your package constraint *@dev

Hope this helps.

Pollux

luceos is your package constraint `*@Davis

I guess you mean *@dev ?

luceos

Pollux wow that mention was hijacking through my tilde, nice catch ?

DiegoPino

luceos I am not an expert in programming but I really like studying its environment and development for testing @luceos Thank You So Much and the community for the support, I am very happy because now have the development environment are ready and its very easy with composer

development environment are ready

Davis

luceos from now on there’s a new branch of development called *@Davis and it’s marked only when the code is perfect.

manny

For example, I would like to work on an existing repository such as flagrow/byobu . I did following:
- git clone for repo flagrow/byobu in the folder workbench
- remove existing subfolder flagrow/byobu
- change value of extension flagrow/byobu to *@dev under the require in the composer.json file (root of flarum) >"flagrow/byobu": "*@dev"

What I all got is following info: - Installing flagrow/byobu (0.1.2): Loading from cache

It is not symlinked to workbench. What am I doing wrong?

jordanjay29

manny you can manually dump the composer cache with composer clear-cache. Try that and then reattempt.

manny

I have dumped the cache and tried to install extensions again. Still no effect. Here the log from terminal:
- Installing flagrow/byobu (0.1.2): Downloading (100%)

I have also put the extension under the require-dev, also no luck. The strange thing is, when I tried with reflar/reactions, it worked. It was symlinked to the workbench.

luceos

manny - remove existing subfolder flagrow/byobu

where did you remove that?

manny

luceos it was located in the vendor folder flagrow. I deleted it manually and also tried with composer remove flagrow/byobu .

luceos

manny did you add this section to the composer.json of the flarum installation (not your extension(s)):


    "repositories": [
        {
            "type": "path",
            "url": "workbench/*/"
        }
    ],

manny

Yes, I did in the root of flarum installation.

luceos

manny ? okay so i got it.

byobu master is for beta 8; you can't install it with beta 7(.1), either also load flarum/core dev-master or clone based on the latest tag compliant with beta 7, using:

git clone git@github.com:flagrow/byobu -b 0.1.2

manny

luceos Ah, makes sense now. It worked, thanks!

luceos

manny also please consider creating a pull request against byobu instead of forking to a new extension ?

andybalaam

I wrote up how I applied this on my local Ubuntu machine here: http://www.artificialworlds.net/blog/2018/09/06/writing-a-new-flarum-extension-on-ubuntu/ please let me know where I went wrong or how I could improve it, thanks!

Pherinos

luceos make sure it follows all guidelines for an extension

This page does not exists any more... 🙁

clarkwinkelmann

Pherinos I updated the link. It's now https://flarum.org/docs/extend/start.html

Walid

clarkwinkelmann the new correct link is https://docs.flarum.org/extend/start

« Previous Page