Hi.
I installed Discourse by instructions found here.
I added the lines in app.yml
I rebuilt the app:
cd /var/discourse
./launcher rebuild app
Plugins do not show up
What am I doing wrong?
Thank you
Hi.
I installed Discourse by instructions found here.
I added the lines in app.yml
I rebuilt the app:
cd /var/discourse
./launcher rebuild app
Plugins do not show up
What am I doing wrong?
Thank you
Hi @kdiamond
Have you read this topic yet?
Yes, I have.
I have a standard install. I installed it on my Ubuntu server by the steps of the standard install following the link here
I have an SSH access to my Ubuntu server.
It seems like you’re doing everything right. You don’t have two sites do you and are updating the second and looking at the first?
No, I have only one site
But I can not find the plugins folder anywhere. Maybe the system fails to create a folder due to some permissions. Just guessing.
This is what happens after ./launcher rebuild app
Everything seems to go smoothly, no error logs
ah wait. Disk space. Just saw it…
Now it makes sense
That looks like it’s the blocker. Without the space it’s not actually starting the rebuild process.
Is this a “local” VM?
Try using growpart
, lvextend
, and resize2fs
to expand your main disk partition.
https://linux.die.net/man/8/resize2fs
Yes, It’s a local VM on VirtualBox
solved it by resizing the volume
sudo df -h
sudo lsblk
sudo pvs
sudo pvresize /dev/sda3
sudo lsblk
sudo lvextend -l+100%FREE /dev/mapper/ubuntu–vg-ubuntu–lv
sudo resize2fs /dev/mapper/ubuntu–vg-ubuntu–lv
Now plugins show up.
Thank you!
Normally you’d play with a dev-install locally and use the standard install on a cloud VPS with a static public IP for Production, but great you’ve got it working
Robert.
Normally?
I was under the impression that following the official step-by-step standard instalation instructions, I have it normally as it gets
Also, please know I’m not an advanced Linux user and this is my first Discourse install.
Thank you
The standard install is for production use in the cloud.
For kicking tires locally you are better to use a development install.
Yes, looking at it now. Would be easier I guess.
Thank you for a suggestion.
I would say that unless you plan on doing plugin development it’s much easier to spin up a standard install. There are a bunch of tricky pieces getting a development install to work.
Otoh, if a domain name and dns are hard for you, then a dev install might be easier.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.