marcus

A little update on timing (of 0.4.0): Right now I'm drowning in client work and simultaneously many PR's are coming in (which is totally cool!). Since there's a public holiday mid-May here in Germany, I hope to find the time to release 0.4.0 then, together with a microsite containing better documentation (which is necessary as the last posts here proove), some info on contributing, gathered knowledge especially on Windows and MAMP/Mac usage. Also, clsource has raised the totally valid point of testing. While Symfony Console is more than ready I'm not sure how to mock/fake/implement the ProcessWire API layer (but also I'm kind of novice in testing). Has anyone an idea of how to do so (maybe it's much easier than I think)? Either way - thanks on input!

Thanks, but I prefer to keep the visual language simpler and the reference to PW subtle (its brand colors).

People, this is really awesome! When I started this little project I had a little hope for community contributions a) because of the vibrant PW community and b) the modular architecture of Symfony Console, but I would have never expected this growth within a month. Big thanks to all contributing and fixing commands and ideas! @horst: Bam! Delivered! Cheers! I'll look into it, merge it soon and will establish a proper namespace for the growing number of helper classes. One more thing: I hate to have hobby horse projects without at least a rudimentary logo

That's a good idea! Instead of status:submodule I'd suggest to add it as options, like: $ wireshell status --php --filesystem --image --webserver ...and output each block/topic as a separate table (see screenshot above). Without options wireshell status would just return the PW and wireshell info. Either way: I'll look into Diagnostic Tools as soon as I finish 0.4.0 and the project microsite. Of course pull requests for this, maybe from the Diagnostic Tools creators & contributors themselves, would be highly appreciated

Thanks, felix! New on develop branch: $ wireshell status (Replacing ShowAdminUrlCommand, ShowVersionCommand)

That would be great!

justb3a's great ModuleDownloadCommand has just hit the develop branch! Next, I'll try to incorporate Nico's module generator, and then both new Commands will be released as 0.4.0 @horst: Thanks for sharing your approach! Since the Readme and this topic's start post is getting bigger and bigger I'll set up a dedicated microsite for wireshell doc and best practices like these.

Haha, talking about biased comparisons - And we're holding back...

Just received the mail from GitHub! Nice! Trying it out over the weekend! Big thanks!

Amazing tool, looks massively helpful! Thanks! (Could we put your generator into a wireshell command, kind of like Mike suggested some days ago?)

Misunderstanding: rename htaccess.txt to .htaccess

Add the contents of this (being the necessary original contents of PWs htaccess) below the line you discovered: https://raw.githubusercontent.com/ryancramerdesign/ProcessWire/master/htaccess.txt

Is a .htaccess file present in the root of your project?

In these cases I'd give the pages menu-1 and menu-2 a template, consisting of: <?php /** * Template: First Child redirect * */ if($page->numChildren) $session->redirect($page->child()->url); So that a click on them redirects to menu-1-1 or menu 2-1 respectively. More: https://processwire-recipes.com/recipes/quick-first-child-redirect/

Not hard at all - fun, as I'm dealing with amazing tools (ProcessWire, Symfony, Composer packages) and learn a lot on the way

Thanks! The idea behind backup:db is that backup is the entity/namespace, and you can specify: :db for database :files for /site/assets/files :scripts for all scripts (/site + /wire + root files) :all for :scripts + :db

Thanks for the support on this - I'll outline the cygwin scenario in the installation instructions. /edit: Updated start post and WS to 0.3.1

Thanks so far! I discovered an installation guide for "laravel install" on windows: http://www.bitspedia.com/2014/09/how-to-install-and-make-first-laravel.html : And when I googled "windows Path environmental variable", got this: http://www.computerhope.com/issues/ch000549.htm. This GUI/matrix seems to be the counterpart to .bashrc.

Since Wireshell is on packagist now and "composer global require wireshell/wireshell" installs it into "~/.composer/vendor/bin/wireshell" on Linux, could you test/check what the comparable Windows path or workflow would be? I'm currently rewriting (simplifying) the installation guide. Cheers!