Not enough space to rebuild

[kdiamond]

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

[Lilly]

Hi @kdiamond
Have you read this topic yet?

Install Plugins in Discourse

This guide assumes that you have a self-hosted standard installation. We only support the standard method of install here, so these instructions assume you have a standard install. This guide only applies to self-hosted Discourse instances. If you are using a managed hosting service, the available plugins are controlled by your hosting provider. For example, on our hosting these specific plugins are available by hosting tier. In this tutorial, we’ll install the Discours…

[kdiamond]

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.

[JammyDodger]

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?

[kdiamond]

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

[kdiamond]

ah wait. Disk space. Just saw it…

Now it makes sense

[JammyDodger]

That looks like it’s the blocker. Without the space it’s not actually starting the rebuild process.

[kdiamond]

Seems strange as VM has 50Gb of storage ¸

but the df -h shows this

[merefield (Robert)]

Is this a “local” VM?

[hello-smile6 (9pfs)]

Try using growpart, lvextend, and resize2fs to expand your main disk partition.
https://linux.die.net/man/8/resize2fs

Auto expand last partition to use all unallocated space, using parted in batch mode

How do I extend a partition with a LVM and the contained physical volume and logical volume?

[kdiamond]

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!

[merefield (Robert)]

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

[kdiamond]

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

[merefield (Robert)]

The standard install is for production use in the cloud.

For kicking tires locally you are better to use a development install.

[kdiamond]

Yes, looking at it now. Would be easier I guess.

Thank you for a suggestion.

[pfaffman (Jay Pfaffman)]

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.