People ask this all the time places like stack exchange and Unix.com (I think that’s a thing) and other sites about system administration. It’s not really a Discourse issue.
Discourse typically keeps stuff in /var/discourse and wherever docker keeps its stuff.
Assuming you have already created a file system on the partition
mkdir /var/discourse
mount /dev/sda4 /var/discourse
But for it to survive a reboot, you will need to create an /etc/fstab entry, and the link I posted in the previous post will explain to you how to do that.
Mounted it and created all the necessary needed things for it to survive but when I install one thing it tells me I can’t install another one on the same hdd…!
Your pointers worked and were useful enough to partition the hdd but to install 2 things isn’t going well
I have 2TB dedicated server with 16GB RAM installed Debian 10 on it to do the following:
Before continue, I already run Discourse on a small VPS of 20Gb SSD with 2GB RAM. The site is getting noticed and growing and I thought of moving it to the 2TB.
Here it goes:
Install a seedbox on almost 1.6TB.
Install a control panel to test and run software and scrips for about 300GB
Install 100GB of it to run Discourse on it.
The problem I get into is; when I install the seedbox it goes well and smooth and when I install VestaCP on the next partition which is mounted and prepared in the command;
The problem is when I install vestacp it goes smooth and runs perfect on the selected partition but when I install the seedbox afterwards, it doesn’t go smooth and gets stuck on:
It will take approx 10 minutes for the script to complete
Updating package lists
Upgrading packages
Installing required packages
Here it takes 2 hours and nothing goes beyond. On the other hand, when I check Vestacp, I see NGINX is disabled because the seebox is trying to take over!
Please don’t take this the wrong way but why are you asking this on the Discourse forum when you didn’t even get to the Discourse installation yet? I think you’ll need to find people who know about Vestacp (which I have never even heard of, sorry).
That, and if I were you I would run some kind of VM platform on that dedicated box to have endless flexibility in what I was doing next.
And if this is just a single drive why bother to partition it into a bunch of tiny pieces that can only cause your grief? Back in the day you had to because file systems were too small (unless you made the blocks big, I think), but except for having a small boot partition there really isn’t reason to partition drives into smaller parts. People now are more likely to combine drives into bigger partitions with RAID, but as all have said, this isn’t a Discourse issue.
There is a topic about how to move to a new server that I can’t find.