search

heimdallrj / wordpress-cli

[DEPRECATED] A command-line toolkit for WordPress Development
https://www.npmjs.com/package/wordpress-cli
MIT License
1 stars 3 forks source link

Add the ability to change the default port #47

Closed THPubs closed 7 years ago

THPubs commented 7 years ago

Now people can use the flag -p or --port to define their port. The script will also update the database's siteurl and home according to the new port to prevent WordPress from re-directing to the old port.

Also added the alias s to serve for lazy people like me :wink: and colored the errors in red.

Solves #15

Hope you like the changes :smile:

heimdallrj commented 7 years ago

@THPubs Wow! Great 👍 Will merge this.

THPubs commented 7 years ago

@thinkholic Cool! Thanks :smile:

heimdallrj commented 7 years ago

@THPubs

Something not directly related to the PR.

Just published a node wrapper for WP-CLI and hoping to integrate it with this. See: https://github.com/kodeflex/node-wp-cli

Plus, hoping to change the project name as wp-artisan. Any opinion? :)

THPubs commented 7 years ago

The idea of the node wrapper is cool. I like it :-)

The name is also good but one small concern... artisan is a good name but, some people might find it hard to remember or might misspell it because it's not a common word. What do you think?

THPubs commented 7 years ago

Ah looks like you have already re-named :smile: Anyway I do like the name. Do I have to make a new pull request to the new project?

heimdallrj commented 7 years ago

Ah looks like you have already re-named 😄 Anyway I do like the name. Do I have to make a new pull request to the new project?

No nop. Still considering, anyway I reserved the namespace. If you have a suggestion let's discuss. Actually I too have some concerns. Name is cool, but remembering is kinda hard like you told. Plus, there is a website with that name too. :/

THPubs commented 7 years ago

Ahaa then it's a problem. I'll also think and see :smile: