Kdtyjb

What does it take to become a wilderness skills guide as a business?

Why do we say 'Pairwise Disjoint', rather than 'Disjoint'?

Sort Array By Month & Year | JavaScript

If nine coins are tossed, what is the probability that the number of heads is even?

Does the US political system, in principle, allow for a no-party system?

Create chunks from an array

What can I do if someone tampers with my SSH public key?

How to add theme from github with composer

SHA 256 Algorithm

Help! My Character is too much for her story!

Use Mercury as quenching liquid for swords?

How to make sure I'm assertive enough in contact with subordinates?

Unfamiliar notation in Diabelli's "Duet in D" for piano

Increase the space between numerator and denominator

How spaceships determine each other's mass in space?

Paper published similar to PhD thesis

School performs periodic password audits. Is my password compromised?

What is Tony Stark injecting into himself in Iron Man 3?

Should we avoid writing fiction about historical events without extensive research?

A running toilet that stops itself

How to write a chaotic neutral protagonist and prevent my readers from thinking they are evil?

Can inspiration allow the Rogue to make a Sneak Attack?

Rationale to prefer local variables over instance variables?

What is the oldest European royal house?

How to add theme from github with composer

How can I include a third party library in my custom module without using Composer ManagerWhere and how should I use Composer and the drupal-composer/drupal-project scaffold to install the required libraries?Installing Bootstrap theme using ComposerIs Composer incapable of updating a project that has already been installed from the .zip distribution?how to import library from Github when the installed module in Drupal 8How do I use composer with modules?Installing a site with composerDrupal install with composer (drupal-project)Can I remove dependencies from dependencies via composer?Support composer_manager AND drupal-composer/drupal-project with contrib module

2

1

I have a Drupal 8 installation and I like to install a theme from github.com using composer.

It is this theme https://github.com/forumone/gesso

Can anybody help me what I have to add to the composer.json and where?

8 installing composer

share|improve this question

edited 2 hours ago

kiamlaluno♦

80.5k9132249

asked 3 hours ago

lesley n.lesley n.

3561418

add a comment | 

2

1

I have a Drupal 8 installation and I like to install a theme from github.com using composer.

It is this theme https://github.com/forumone/gesso

Can anybody help me what I have to add to the composer.json and where?

8 installing composer

share|improve this question

edited 2 hours ago

kiamlaluno♦

80.5k9132249

asked 3 hours ago

lesley n.lesley n.

3561418

add a comment | 

I have a Drupal 8 installation and I like to install a theme from github.com using composer.

It is this theme https://github.com/forumone/gesso

Can anybody help me what I have to add to the composer.json and where?

8 installing composer

share|improve this question

edited 2 hours ago

kiamlaluno♦

80.5k9132249

asked 3 hours ago

lesley n.lesley n.

3561418

share|improve this question

edited 2 hours ago

kiamlaluno♦

80.5k9132249

asked 3 hours ago

lesley n.lesley n.

3561418

share|improve this question

edited 2 hours ago

kiamlaluno♦

80.5k9132249

asked 3 hours ago

lesley n.lesley n.

3561418

edited 2 hours ago

kiamlaluno♦

80.5k9132249

edited 2 hours ago

kiamlaluno♦

80.5k9132249

asked 3 hours ago

lesley n.lesley n.

3561418

asked 3 hours ago

lesley n.lesley n.

3561418

3 Answers
3

active

oldest

votes

2

If you still want download theme from github, you can edit file composer.json by add more repository:

Add this code

 {

    "type": "package",

    "package": {

        "name": "forumone/gesso",

        "version": "2.0",

        "type":"drupal-theme",

        "source": {

            "url": "https://github.com/forumone/gesso.git",

            "type": "git",

            "reference": "8.x-2.x"

        }

    }

}

after

{

    "type": "composer",

    "url": "https://packages.drupal.org/8"

},

and run composer require "forumone/gesso"
to download theme and update composer.lock.

share|improve this answer

answered 2 hours ago

JonhJonh

345120

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to clarify here, the dev branch for this theme is parallel on both GitHub and drupal.org. Alternatively, one could do composer require drupal/gesso:2.x-dev to get the dev branch. To me it looks exactly the same. So, you don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on d.o. at all, 99% of the time they are on packagist (third party vendor). The rare case is when you have a private repo on GitHub, then this is the approach you would want to take.
  
  – Kevin
  1 hour ago
  
  
  

  
  
  
  

add a comment | 

3

Adding this answer for more clarification for future readers:

The theme in question as of this comment date has a stable release from April 2018. But the development branch is active and updated.

In such a case, you would do this to fetch it instead of the latest stable:

composer require drupal/gesso:2.x-dev

To go even further, you can tack a commit sha on the end of the version to 'pin` the code at that commit - unless you want rolling updates from HEAD. This is a versatile option that you can opt for in Composer that is not so known in the Drupal circles.

You don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on drupal.org at all, 99% of the time they are on Packagist (third party packages, like Prophecy etc).

The rare case is when you have a private repo on GitHub/GitLab or elsewhere, then this is the approach you would want to take to fetch it.

share|improve this answer

answered 1 hour ago

KevinKevin

18.2k853113

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is a good answer, because you give the advice of best practice. So I've learned a lot today. How to add package to composer.json and how to use dev-version with cli command.
  
  – lesley n.
  45 mins ago
  
  
  

  
  
  
  

add a comment | 

1

You shouldn't use the Github repository, unless you're getting involved in the theme's development - it doesn't contain a composer.json file, so isn't supposed to be installed this way.

You could mess about trying to set it up as a custom repository, but given that this is a theme hosted on (and packaged by) drupal.org, it would be easier to just install it the standard way:

composer require drupal/gesso

share|improve this answer

answered 3 hours ago

Clive♦Clive

148k13250292

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  on drupal.org the files are from last year and on github from this year. That's why I want to install from github.
  
  – lesley n.
  3 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You would have to add the github repo as a new repository item and call it that way. It isn't ideal, and the Gesso theme should have updated its d.o. project as thats where everyone expects to obtain packages. getcomposer.org/doc/05-repositories.md
  
  – Kevin
  2 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What @Kevin said. And just to add that when code isn't in a stable branch, it's often because it's not considered to be stable. i.e. don't run it in production without a plenty of testing. You can find out how to add a custom github repository in the composer docs, just make sure you have type: drupal-module if you want it to be moved into the correct folders etc when installing
  
  – Clive♦
  2 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @lesleyn. The development snapshot has been updated on February, 2019. If you want to know when the next official release will be made, you can check/ask on the theme issue queue, on drupal.org.
  
  – kiamlaluno♦
  2 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "220"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdrupal.stackexchange.com%2fquestions%2f277469%2fhow-to-add-theme-from-github-with-composer%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

If you still want download theme from github, you can edit file composer.json by add more repository:

Add this code

 {

    "type": "package",

    "package": {

        "name": "forumone/gesso",

        "version": "2.0",

        "type":"drupal-theme",

        "source": {

            "url": "https://github.com/forumone/gesso.git",

            "type": "git",

            "reference": "8.x-2.x"

        }

    }

}

after

{

    "type": "composer",

    "url": "https://packages.drupal.org/8"

},

and run composer require "forumone/gesso"
to download theme and update composer.lock.

share|improve this answer

answered 2 hours ago

JonhJonh

345120

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to clarify here, the dev branch for this theme is parallel on both GitHub and drupal.org. Alternatively, one could do composer require drupal/gesso:2.x-dev to get the dev branch. To me it looks exactly the same. So, you don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on d.o. at all, 99% of the time they are on packagist (third party vendor). The rare case is when you have a private repo on GitHub, then this is the approach you would want to take.
  
  – Kevin
  1 hour ago
  
  
  

  
  
  
  

add a comment | 

2

If you still want download theme from github, you can edit file composer.json by add more repository:

Add this code

 {

    "type": "package",

    "package": {

        "name": "forumone/gesso",

        "version": "2.0",

        "type":"drupal-theme",

        "source": {

            "url": "https://github.com/forumone/gesso.git",

            "type": "git",

            "reference": "8.x-2.x"

        }

    }

}

after

{

    "type": "composer",

    "url": "https://packages.drupal.org/8"

},

and run composer require "forumone/gesso"
to download theme and update composer.lock.

share|improve this answer

answered 2 hours ago

JonhJonh

345120

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just to clarify here, the dev branch for this theme is parallel on both GitHub and drupal.org. Alternatively, one could do composer require drupal/gesso:2.x-dev to get the dev branch. To me it looks exactly the same. So, you don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on d.o. at all, 99% of the time they are on packagist (third party vendor). The rare case is when you have a private repo on GitHub, then this is the approach you would want to take.
  
  – Kevin
  1 hour ago
  
  
  

  
  
  
  

add a comment | 

If you still want download theme from github, you can edit file composer.json by add more repository:

Add this code

 {

    "type": "package",

    "package": {

        "name": "forumone/gesso",

        "version": "2.0",

        "type":"drupal-theme",

        "source": {

            "url": "https://github.com/forumone/gesso.git",

            "type": "git",

            "reference": "8.x-2.x"

        }

    }

}

after

{

    "type": "composer",

    "url": "https://packages.drupal.org/8"

},

and run composer require "forumone/gesso"
to download theme and update composer.lock.

share|improve this answer

answered 2 hours ago

JonhJonh

345120

 {

    "type": "package",

    "package": {

        "name": "forumone/gesso",

        "version": "2.0",

        "type":"drupal-theme",

        "source": {

            "url": "https://github.com/forumone/gesso.git",

            "type": "git",

            "reference": "8.x-2.x"

        }

    }

}

{

    "type": "composer",

    "url": "https://packages.drupal.org/8"

},

share|improve this answer

answered 2 hours ago

JonhJonh

345120

answered 2 hours ago

JonhJonh

345120

answered 2 hours ago

JonhJonh

345120

3

Adding this answer for more clarification for future readers:

The theme in question as of this comment date has a stable release from April 2018. But the development branch is active and updated.

In such a case, you would do this to fetch it instead of the latest stable:

composer require drupal/gesso:2.x-dev

To go even further, you can tack a commit sha on the end of the version to 'pin` the code at that commit - unless you want rolling updates from HEAD. This is a versatile option that you can opt for in Composer that is not so known in the Drupal circles.

You don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on drupal.org at all, 99% of the time they are on Packagist (third party packages, like Prophecy etc).

The rare case is when you have a private repo on GitHub/GitLab or elsewhere, then this is the approach you would want to take to fetch it.

share|improve this answer

answered 1 hour ago

KevinKevin

18.2k853113

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is a good answer, because you give the advice of best practice. So I've learned a lot today. How to add package to composer.json and how to use dev-version with cli command.
  
  – lesley n.
  45 mins ago
  
  
  

  
  
  
  

add a comment | 

3

Adding this answer for more clarification for future readers:

The theme in question as of this comment date has a stable release from April 2018. But the development branch is active and updated.

In such a case, you would do this to fetch it instead of the latest stable:

composer require drupal/gesso:2.x-dev

To go even further, you can tack a commit sha on the end of the version to 'pin` the code at that commit - unless you want rolling updates from HEAD. This is a versatile option that you can opt for in Composer that is not so known in the Drupal circles.

You don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on drupal.org at all, 99% of the time they are on Packagist (third party packages, like Prophecy etc).

The rare case is when you have a private repo on GitHub/GitLab or elsewhere, then this is the approach you would want to take to fetch it.

share|improve this answer

answered 1 hour ago

KevinKevin

18.2k853113

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is a good answer, because you give the advice of best practice. So I've learned a lot today. How to add package to composer.json and how to use dev-version with cli command.
  
  – lesley n.
  45 mins ago
  
  
  

  
  
  
  

add a comment | 

Adding this answer for more clarification for future readers:

The theme in question as of this comment date has a stable release from April 2018. But the development branch is active and updated.

In such a case, you would do this to fetch it instead of the latest stable:

composer require drupal/gesso:2.x-dev

To go even further, you can tack a commit sha on the end of the version to 'pin` the code at that commit - unless you want rolling updates from HEAD. This is a versatile option that you can opt for in Composer that is not so known in the Drupal circles.

You don't need to pull from GitHub in this instance. The only time you would want to do this is when a package does not live on drupal.org at all, 99% of the time they are on Packagist (third party packages, like Prophecy etc).

The rare case is when you have a private repo on GitHub/GitLab or elsewhere, then this is the approach you would want to take to fetch it.

share|improve this answer

answered 1 hour ago

KevinKevin

18.2k853113

share|improve this answer

answered 1 hour ago

KevinKevin

18.2k853113

answered 1 hour ago

KevinKevin

18.2k853113

answered 1 hour ago

KevinKevin

18.2k853113

1

You shouldn't use the Github repository, unless you're getting involved in the theme's development - it doesn't contain a composer.json file, so isn't supposed to be installed this way.

You could mess about trying to set it up as a custom repository, but given that this is a theme hosted on (and packaged by) drupal.org, it would be easier to just install it the standard way:

composer require drupal/gesso

share|improve this answer

answered 3 hours ago

Clive♦Clive

148k13250292

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  on drupal.org the files are from last year and on github from this year. That's why I want to install from github.
  
  – lesley n.
  3 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You would have to add the github repo as a new repository item and call it that way. It isn't ideal, and the Gesso theme should have updated its d.o. project as thats where everyone expects to obtain packages. getcomposer.org/doc/05-repositories.md
  
  – Kevin
  2 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What @Kevin said. And just to add that when code isn't in a stable branch, it's often because it's not considered to be stable. i.e. don't run it in production without a plenty of testing. You can find out how to add a custom github repository in the composer docs, just make sure you have type: drupal-module if you want it to be moved into the correct folders etc when installing
  
  – Clive♦
  2 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @lesleyn. The development snapshot has been updated on February, 2019. If you want to know when the next official release will be made, you can check/ask on the theme issue queue, on drupal.org.
  
  – kiamlaluno♦
  2 hours ago
  

  
  
  
  

add a comment | 

1

You shouldn't use the Github repository, unless you're getting involved in the theme's development - it doesn't contain a composer.json file, so isn't supposed to be installed this way.

You could mess about trying to set it up as a custom repository, but given that this is a theme hosted on (and packaged by) drupal.org, it would be easier to just install it the standard way:

composer require drupal/gesso

share|improve this answer

answered 3 hours ago

Clive♦Clive

148k13250292

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  on drupal.org the files are from last year and on github from this year. That's why I want to install from github.
  
  – lesley n.
  3 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  You would have to add the github repo as a new repository item and call it that way. It isn't ideal, and the Gesso theme should have updated its d.o. project as thats where everyone expects to obtain packages. getcomposer.org/doc/05-repositories.md
  
  – Kevin
  2 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What @Kevin said. And just to add that when code isn't in a stable branch, it's often because it's not considered to be stable. i.e. don't run it in production without a plenty of testing. You can find out how to add a custom github repository in the composer docs, just make sure you have type: drupal-module if you want it to be moved into the correct folders etc when installing
  
  – Clive♦
  2 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @lesleyn. The development snapshot has been updated on February, 2019. If you want to know when the next official release will be made, you can check/ask on the theme issue queue, on drupal.org.
  
  – kiamlaluno♦
  2 hours ago
  

  
  
  
  

add a comment | 

You shouldn't use the Github repository, unless you're getting involved in the theme's development - it doesn't contain a composer.json file, so isn't supposed to be installed this way.

You could mess about trying to set it up as a custom repository, but given that this is a theme hosted on (and packaged by) drupal.org, it would be easier to just install it the standard way:

composer require drupal/gesso

share|improve this answer

answered 3 hours ago

Clive♦Clive

148k13250292

composer require drupal/gesso

share|improve this answer

answered 3 hours ago

Clive♦Clive

148k13250292

answered 3 hours ago

Clive♦Clive

148k13250292

answered 3 hours ago

Clive♦Clive

148k13250292