In reply to Neo.

Thanks Neo, that’s a good point. Here’s a list of the top 10 reasons why TasteWP may still be required even if you know how to set up a local environment:

1) Set up is quicker: on TasteWP it takes 5 seconds max, while on local you need to unzip the WordPress installation files, set up the site etc.

2) Real-life environment: TasteWP is closer to what your users will experience, i.e. it comes with all limits (e.g. timeout limits; also we block common functions which almost all public hosters do), so you can detect issues which would have gone unnoticed in local environments.

3) Different WP versions: You can simply set up different versions of WordPress (also saves time)

4) *Change PHP version quickly”: Saves time (most users don’t know how to install multiple PHP versions on local)

5) SSL: TasteWP sites come with SSL out of the box, no need to generate it, again saving time.

6) *Keep your PC clean”: Most of local environments are used for short-term testing only, so after you’re done you have to clean it up again (which you don’t have to worry about on TasteWP)

7) Debug friendly:
– TasteWP allows to quickly prepare different wp-configs with custom settings
– By default you can access your debug file under /debug.log or /wp-content/debug.log
– You have all temporary files in one place, so you can find issues of your plugin / theme if it uses temp files (/tmp)
– You can quickly disable all plugins from dashboard in case your plugin crashed something (and upload fixed version, without removing the site)

8) No need to remember passwords: You can login with one click from the dashboard, making management easier (especially relevant if you use multiple sites)

9) Multisite: You can also test your plugin on multisite which sometimes can be problematic on local environments, saving you time.

10) Share it with others: You can share it with other people from your team to show progress (helps with relations, makes you look professional)

I hope at least some of those are also valid for you 🙂