Docker – how much WordPress to “expose” via volume/maps

  • Hi guys.

    While having your WordPress in Docker and thinking of redundancy – say you want a couple of redundant, standby nodes to be ready to take over in fail-over fashion – how much of WordPress, its code in flat files, you mount/expose to the host so then that data/content can be mirrored to those standby nodes?

    Should it be the whole lot or perhaps only specific dir structure locations?

    I read people, when they share theirs stories, suggest different things, which sometimes will be ‘/var/www/html'(which I gather is whole WordPress?) mapped to host and other times only some subdirs, but I failed to find a guide/howto which would discuss that “issue” from that “WordPress data redundancy” perspective.

    Any idea or experience shared I’ll very much appreciate.
    many thanks, L

    • This topic was modified 3 years, 9 months ago by Jan Dembowski. Reason: Moved to Fixing WordPress, this is not an Developing with WordPress topic
Viewing 1 replies (of 1 total)

  • /var/www/html

    Contains both code and data

    in a normal installation the data components that are not database items are held in
    /var/www/html/wp-content/uploads
    these are mainly but not exclusively image / media files

    If you want a node to be able to instantly take over then replicating /var/www/html and the db would give you a full solution in my opinion.

    I don’t think the solution differs whether in docker or just non containerised server.

    I think other may chime in, my experience of building highly redundant WP solutions is limited.

    • This reply was modified 3 years, 9 months ago by Alan Fuller.
Viewing 1 replies (of 1 total)
  • The topic ‘Docker – how much WordPress to “expose” via volume/maps’ is closed to new replies.

Tags