Docs regarding pnpm with ghost install

Developer help Installation
1

I notice that everytime i run $ghost install local, I end up with a directory ~380mb in size, which means for every project I’m building on ghost, I need that amount of disk space.

I’m currently working on older hardware and limited disk space. Also data costs per gb here and I’m assuming $ghost install local downloads the entire codebase and dependencies everytime i run it. Is there a way for me to reduce disk space by installing Ghost via pnpm so that node_modules are shared? I installed ghost cli via pnpm.

For reference I found this pr: pnpm by AlexMunoz · Pull Request #164 · slinkity/slinkity · GitHub

I’m on Linux.

2

For reference, I’m symlinking to solve the disk space issue for local dev:

ghost1/current -> ../ghostcore/versions/5.94.1
ghost2/current -> ../ghostcore/versions/5.94.1
ghostcore/versions/5.94.1

Then edit config.dev…json and .ghost-cli. ghost1 & ghost2 use 2.8mb in disk space.

This seems to be working, but I’m sure its not considered a good practice nor the best way to reduce disk space usage, considering the manual interventions and future potential issues when using ghost-cli

3

there’s also a config file in ~/.ghost/config that needs to be edited to account for each Ghost installation

4

Following with interest! I currently have um… 37 Ghost installs (ish) across two WSL distros, and um… I need help! :)

5

I had to look up what “WSL distro” means :slightly_smiling_face: 37x~380mb certainly does add up. I’m busy working on two Ghost+Astro projects using the symlinked method and everything seems to be running smooth.

Editing the ~/.ghost/config file just alerts ghost cli that there is another install so that when you run $ghost ls, all of your Ghost projects are listed.

I’d wait a little for more knowledgeable Ghost engineers to chime in before adjusting your setup though