Why Nostr?What is Njump?
pailakapo
npub17cw…alhd
2024-05-20 06:54:32
in reply to nevent1q…90e5

pailakapo on Nostr: So let’s look at the docker-compose.yml file. There are 3 sections: Version, ...

So let’s look at the docker-compose.yml file.

There are 3 sections:
Version, services, and volumes.

Version is 3.8. I’ll leave that until I see something different.

In Services, the guide installs nginxproxymanager, but I already have that running, so I’ll skip that.

In that section there’s also blossom-drive and blossom-server.

I will be installing blossom-drive, and for this section it looks like I just need to switch the ports from 80:80 to something else, like 2080:80, since port 80 on the server is already used.

Under blossom-server I’ll change ports from 3000:3000 to 3200:3000 since 3000 is also used on the server.
For volumes, I think this maps server volumes from:to volumes inside the docker.
There are two volumes mapped in the guide:

1. './blossom-server/config.yml:/app/config.yml'
2. 'blossom_data:/app/data'

Both are mapped to the “app” directory inside the docker, so I think both should be /mnt/user/appdata in my setup.

In that case, I should create config.yml in the appdata/blossom directory.

But “blossom_data” sounds like the actual images/files maybe? If so I don’t want them in appdata. So I’ll need to look into that.

First I should get the docker running, save an image and see where it puts things, then I can make changes and run it again.

Last section in the docker-compose is Volumes.

This says: blossom_data:
Which doesn’t seem to map this to anything inside the docker. Not sure what to do here.

#grownostr #blossom #asknostr
Author Public Key
npub17cwgazyy9ahc0fu2cslql8w5csxg77zramt9rzel09yvxvrjk2eqntalhd