Installing WordPress With Clean Subversion Repositories

  • Resolved ScratchMonkey

    (@scratchmonkey)


    4 years, 7 months ago

    Should this guide still work?

    If I check out trunk, it looks like the docroot is the src subdirectory. So the instructions seem to want me to put wp-config.php in the root of the checked-out working directory. It seems like that ruins the point of the exercise, to not pollute the working copy with site-specific files. Is there an updated version of these instructions? Should I be checking out the src directory and not getting all the tools? That seems to violate the spirit of the repo reorganization.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter ScratchMonkey

    (@scratchmonkey)

    I just realized the protected link is supposed to go to my site. That’s not what I need help with. It’s how to organize the files on the web server so I can keep the svn working directory clean. As originally explained here:

    https://codex.www.ads-software.com/Installing_WordPress_With_Clean_Subversion_Repositories

    Let’s say I’m installing to /home/mysite. That page suggests I check out to /home/mysite/trunk and then create /home/mysite/wp-config.php in the directory above trunk to avoid polluting the working copy.

    But the new layout puts the docroot in /home/mysite/trunk/src, so I’d have to put my wp-config.php in /home/mysite/trunk, which pollutes the WC. How are normal developers organizing their setups to avoid this? It looks like you just depend on the svn:ignore property on trunk.

    Moderator Dion Hulse

    (@dd32)

    Meta Developer

    If you use https://core.svn.www.ads-software.com/ as suggested in the tutorials, you’ll get a “clean” build without the src directory.

    If you’re seeing trunk/src as the folder, then you’re using https://develop.svn.www.ads-software.com/ which is designed as a “source” repo rather than production-ready code. The main difference being that CSS, JS and some PHP files aren’t built ready for use (You’d have to run some npm processes to get it into a state where it’d work in a browser).

    Although core development switched from core.svn to develop.svn you can continue to use the former as it’s automatically updated with the result of the build process (and is where WordPress releases are built from)

    Thread Starter ScratchMonkey

    (@scratchmonkey)

    Thanks. I could swear I looked at the core URL in the source browser and saw a src directory, but now it’s not there. I just have fat-fingered the URL when I tried to inspect it a couple days ago. But looking at it now I see the old layout. Which is good because I need to update an existing site and it would have been slightly painful with that reorg of the directory structure.

    Thread Starter ScratchMonkey

    (@scratchmonkey)

    One additional glitch (which is just a documentation clarification): I ran into the ‘Sorry, you are not allowed to customize this site.’ message and, after much research and figuring out how to enable debugging, revealed that I’d put the extra settings for WP_HOME and WP_CONTENT_DIR at the end of wp-config.php, not before the “stop editing!” line. Turning on WP_DEBUG revealed that right away with a message that those variables were being defined twice. So I’d recommend adding to the guide that those settings must go before the stop-editing line.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Installing WordPress With Clean Subversion Repositories’ is closed to new replies.