This page is an overview of the WP-CLI. It is very powerful tool to be able to generate content truely at the speed of thought.<\/p>\n
I found this plugin that allows me to add indexes to to pages or posts. I am going to use this to create these organizational pages about different categories of information.<\/p>\n
Posts Regarding The WP-CLI<\/span> Here is the main website for the WP-CLI<\/a><\/p>\n First get the Phar file<\/p>\n Now check that it is working:<\/p>\n Now check that WP-CLI was successfully installed<\/p>\n This is more complicated than it should be<\/p>\n Now every time you want to make sure “sudo” uses your current path all you need to do is use “mysudo” like this:<\/p>\n This is the WP-CLI_Index-Page.txt Id has PostId of 5123<\/p>\n","protected":false},"excerpt":{"rendered":" This page is an overview of the WP-CLI. It is very powerful tool to be able to generate content truely at the speed of thought. I found this plugin that allows me to add indexes to to pages or posts.…<\/span><\/p>\n
\n<\/ul><\/p>\n
<\/i><\/a> Installing WP-CLI \u2191<\/a><\/sup><\/h2>\n
\n\/\/\n\/\/\nwget https:\/\/raw.githubusercontent.com\/wp-cli\/builds\/gh-pages\/phar\/wp-cli.phar\n\n<\/pre>\n
\n\/\/\n\/\/\nphp wp-cli.phar --info\n<\/pre>\n
\n\/\/\n\/\/\nchmod +x wp-cli.phar\nsudo mv wp-cli.phar \/usr\/local\/bin\/wp\n<\/pre>\n
\n\/\/\n\/\/\nwp --info\n<\/pre>\n
<\/i><\/a> Updating WP-CLI \u2191<\/a><\/sup><\/h2>\n
\n\/\/\n\/\/You should be able to just do this\nwp cli update\n\n\/\/ But that will give you the following error\nError: \/usr\/local\/bin is not writable by current user.\n\n\/\/ So you have to do\nsudo wp cli update\n\n\/\/ But that will give you a path error like this\n\/usr\/bin\/env: php: No such file or directory\n<\/pre>\n
\nYou should not assume that the $PATH variable set by the currently logged in
\n user is the one that the sudoers are going to use. The “sudo” command uses
\na “secure_path”. You can see the two paths like this:<\/p>\n\n\/\/\n\/\/\nenv | grep ^PATH\nsudo env | grep ^PATH\n\n\/\/ Sudo might be overriding your path.\n\/\/ If you would like to see if the \"secure_path\" do this:\nsudo -V | grep 'Value to override'\n\n\/\/ This will give you the \"secure_path\"\nValue to override user's $PATH with: \/sbin:\/bin:\/usr\/sbin:\/usr\/bin\n\n\/\/ If this is the case you can always edit \"\/etc\/sudoers\" like this:\nvisudo\n\/\/or\nvim \/etc\/sudoers\n\n\/\/ You can force sudo to use the path that you choose like this:\nsudo -E env \"PATH=$PATH\" wp cli update\n\n<\/pre>\n
\n\/\/\n\/\/\n\/\/ Make sure this file exists\ntouch \/etc\/profile.d\/00-aliases.sh\n\/\/ Add this alias to it\nsed -i \"$ a alias mysudo=\\'sudo -E env \\\"PATH=\\$PATH\\\"\\' \" \/etc\/profile.d\/00-aliases.sh\n<\/pre>\n
\n\/\/\n\/\/ so instead of having to remember and type this\nsudo -E env \"PATH=$PATH\" wp cli update\n\n\/\/ You can now do \nmysudo wp cli update\n\n<\/pre>\n<\/div>\n<\/div>\n