P
Postiz•3w ago
Support

Ticket: Docker Setup Folder Structure Guidance Needed

@Moriarte Just created a ticket
Question: What folders do I need in my Docker setup for this to work?
Attempted: I've tried reading the docker compose yaml but i'm still a novice at Docker and don't know exactly how to discern which folders it requires.
Working On: I'm not sure what to put here, I'm working on Postiz?
Using Postiz On: currently using Synology Container Manager and Portainer
Take it from here @Postiz
7 Replies
Moriarte
Moriarte•3w ago
I picked "agency owner" because you don't have an option in your discord setup for "Business owner".
xcons
xcons•3w ago
Heya @Moriarte Is your name from Sherlock Holmes? 🙂 When you deploy Postiz from the docker compose, it should create two volumes for you - postiz-config and postiz-uploads
Moriarte
Moriarte•3w ago
Yeah, it's slightly altered but I do enjoy the moniker. 😄 Synology typically wants the folders to be pre-created so that's where my confusion was. I'll see if running the yaml file in portainer just does it automatically. Synologys are weird about docker.
xcons
xcons•3w ago
hehe You can use a direct path to a folder, like: 
volumes:
  - /mount/uploads/:/uploads
volumes:
  - /mount/uploads/:/uploads
However the default compose config uses container volumes, not directories directly 
    volumes:
      - postiz-config:/config/
      - postiz-uploads:/uploads/
    volumes:
      - postiz-config:/config/
      - postiz-uploads:/uploads/
I'm pretty sure synology could auto-create those two docker volums for you
Moriarte
Moriarte•3w ago
Hmm....portainer keeps failing when just running the compose file Something about a bind address already in use but none of my containers use 5432
xcons
xcons•3w ago
Ah yeah, Synology uses that already for Postgres It's safe to remove this from your compose file; 
ports:
  - 5432:5432
ports:
  - 5432:5432
The public docs should have already removed that
Moriarte
Moriarte•3w ago
Hey, thanks. I'll give that a try today. Okay, the new Docker Compose file in the guide seems to have allowed me to deploy the stack now but it won't let me sign in with google or let me create and account. "General error : TypeError : Failed to fetch. Please check your browser console." I feel like maybe I did something wrong with the URLs. Google sign in button gives a console error of 405 : Method not allowed This seems to also happen with creating an account manually. The console is also throwing a CORS policy error but I'm not sure what that means.

Did you find this page helpful?