mhulse / bueller Goto Github PK

How does the automatic update feature of near future WP's affect GitHub submodule setups?

http://wordpress.org/news/2013/09/wordpress-3-7-beta-1/

Good thread here:

http://wordpress-hackers.1065353.n5.nabble.com/WP-3-7-auto-update-td42437.html

Neet to research/investigate.

I don't use submodules anymore.

Remove from these lines: https://github.com/mhulse/bueller/blob/master/.htaccess#L7-L8

1. Create new repo.
2. Clone repo locally.
3. Add boilerplate files from this repo (don't copy the .gitmodules and wp folder).
4. In terminal, cd to your repo and run $ git submodule add git://github.com/WordPress/WordPress.git wp
5. Next, move to the wordpress folder: $ cd wp.
6. View tags: git fetch --tags && git tag -n.
7. Check out latest tag: $ git checkout 3.8.
8. Commit your changes.

Make note in readme about setting your salts. Maybe link to the official WP installation instructions.

This line:

Include /Applications/XAMPP/etc/extra/httpd-vhosts.confInclude /Applications/XAMPP`

This line:

Duplicate wp-config-sample.php and fill-in the database connection information.

... should say something like:

Duplicate wp-config-sample.php, rename it to wp-config.php, and fill-in the database connection information.

I like this setup for logging errors:

//--------------------------------------------------------------------

/**
 * This will log all errors notices and warnings to a file called
 * `debug.log` in `/wp-content`. If Apache does not have write permission,
 * you may need to create the file first and set the appropriate `666`
 * permissions.
 *
 * ```
 * $ tail -f wp-content/debug.log
 * ```
 *
 * @see http://wordpress.stackexchange.com/a/69552/32387
 */

define('WP_DEBUG', TRUE);
define('WP_DEBUG_LOG', TRUE);
define('WP_DEBUG_DISPLAY', FALSE);
@ini_set('display_errors', 0);

//--------------------------------------------------------------------

/**
 * @see http://codex.wordpress.org/Hardening_WordPress#Securing_wp-config.php
 */

define('DISALLOW_FILE_EDIT', true);

Taken from: Define WP_DEBUG conditionally / for admins only / log errors (append query arg for all links?)

It's root/no password

... and DB_CHARSET? I think their default values are sufficient, and only need to be adjusted if you know what you're doing:

http://codex.wordpress.org/Editing_wp-config.php#Database_collation

The "test everything out" is not linking to the proper documentation. Double check my GH links.

To latest version found here:

https://github.com/mhulse/gh-boiler/blob/master/.gitignore

I need to re-word my statements about cloning. Up until now, I've assumed that the git@github... URIs were for push/pull with the proper credentials.

From what I've read here:

Which remote URL should I use?

... that both will work if you have the creds setup properly.

1. Make note on SSH tunneling and commenting out local db settings
2. Determine where error log appears. Content folder?

Change:

This is a simple starting point for WordPress installs.

... to:

A simple starting point for WordPress installs.

The instructions use ssh to clone. Might want to make note that one should clone this repo and do that, or use HTTPS. After all, this is more "notes to self" than it is "notes to everyone else", so I probably should keep it mostly useful to me, as no one (other than me) will probably ever use this code. 😄

Might want to make not in README of best db collation. I think that's utf8_general_ci.

I want to add TOC style to top of README in order to make things better organized.

See: mhulse/gh-boiler#19

Need a "discussion" section and link to this thread:

http://wordpress-hackers.1065353.n5.nabble.com/GitHub-submodule-theme-development-td41755.html

Officially:

http://lists.automattic.com/pipermail/wp-hackers/2013-July/046334.html