5 posts were split to a new topic: Unable to install plugins
I cant find discourse folder in /var.
i have installed discourse by Bitnami Installer on Mac OSX Yosemite 10.10.2
how do install plugin, because not able to app.yml file
Maybe @chipi92 from Bitnami has some insight on this one?
Bitnami Stacks are auto-contained, it means you can find everything you need to run Discourse under the same folder (aka. installation folder or installdir).
This folder is the one you indicated when you installed the stack either using the GUI installer or the command line.
To install a plugin in your Bitnami Discourse Stack please follow the instructions in our wiki page:
If you have any Bitnami specific question you are welcome to our Bitnami Community forum (run on Discourse BTW):
Thank u @chipi92 it worked
So I added the following to app.yml and did run a rebuild. However none of these plugins show up in my Discourse instance and I don’t know what to do:
## The docker manager plugin allows you to one-click upgrade Discourse ## http://discourse.example.com/admin/docker hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/angusmcleod/discourse-header-search.git - git clone https://github.com/discourse/discourse-solved.git - git clone https://github.com/gdpelican/babble.git - git clone https://github.com/angusmcleod/discourse-topic-previews.git - git clone https://github.com/gdpelican/retort.git - git clone https://github.com/discourse/discourse-staff-notes.git - git clone https://github.com/ligthyear/discourse-plugin-pm-button.git - git clone https://github.com/rux-pizza/discourse-awesome-bbcodes.git - git clone https://github.com/iunctis/discourse-formatting-toolbar.git
Is there an update the allows installing plugin without the whole building process that lasts a few minutes?
In my experience I’ve seen that a single plugin that has a problem can prevent others from being displayed in the Admin -> Plugins page.
A pain, I know, but the only way to find the problem that I know of is to remove them and add them back until the problem happens.
You should be able to leave the “blessed” - “official” Discourse plugins without a problem.
Then gradually add the others in and check the page.
no, there is no way to do so, if you want to minimise downtime during container updates use a data container.
Is there any way to quickly test plugins without rebuilding the whole thing? e.g. minor css/js changes in a plugin. A script or something that will just regenerate a single plugin?
If you want to test stuff quickly you best install a dev environment.
Long term we want to make it easier to disable/enable plugins (and add a “safe mode”) options but for playing around your best option is a dev environment.
I have discourse running in a docker container and have been using
launcher rebuild to test plugin changes. Is this classed as a “dev environment”?
Edit: found this: https://meta.discourse.org/t/development-environment-vagrant-or-docker/12170/8?u=dtbaker Docker = Production, Vagrant = Dev. I’ll ditch my docker install and setup vagrant.
@angus thanks for the changes.
/root/.ssh/config: Directory nonexistent on the first line where it echo’s the string to the config file.
Do I need to create the /root/.ssh folder first?
Is it a problem to install more than one plugin at once?
A potential problem would be installing a broken plugin in the bunch.
Until and unless Discourse has a type of “installed but not activated” feature (i.e. “sandboxed”), IMHO it is better to first install one at a time to make sure it’s OK, then add another
Many thanks for your fast response.
in my running Discourse’s app.yml, there is no “- mkdir -p plugins” line. Do I need to add it when installing a new plugin as its showing in your sample app.yml?
hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git
That’s weird. Yes you have to add this line. When adding a plugin, it should look like this
hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-spoiler-alert.git
It might depend on the way it was set-up.
My localhost file doesn’t have that line yet works fine
## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-data-explorer.git - git clone https://github.com/Mittineague/discourse-plugin-outlet-lo$ - git clone https://github.com/discourse/discourse-solved.git - git clone https://github.com/discourse/discourse-staff-notes.git - git clone https://github.com/Mittineague/discourse-kinder-guardian.$ # - git clone https://github.com/Mittineague/test-plugin.git - git clone https://github.com/iunctis/discourse-formatting-toolbar.g$