If you have a shiny server that doesn’t work, you’re not alone.
There are hundreds of other servers out there.
You can even add shiny servers as a new project, using the awesome new PHP-Server-Plugin plugin.
We’ve tried to list some of the most common shiny server issues here, and to give you a general idea of what to expect from your shiny server.
The shiny server won’t respond to requests¶ It might be a server that’s already running.
You could install the shiny-server-plugin and set it up as a shiny site on your shiny host.
But there’s no guarantee that shiny servers will respond to your requests.
The same is true for PHP-Unit, which runs on shiny servers.
This means that you might get a blank page, no response, or some other strange error.
For this reason, if you install shiny-sbt and add shiny-phpunit as a dependency, shiny servers won’t show up on the new shiny sites you add.
If you’re working on a shiny-static-site project, you’ll probably want to manually add shiny server as a project as well.
The server is blocking your requests¶ If you don’t want shiny servers blocking your PHP scripts, add shiny_server as a composer dependency and disable shiny_phpunit.
If your shiny-app package depends on shiny_sbt, you can disable shiny-ssl by adding shiny_ssl to your composer.json file.
If shiny_app is installed, you might need to manually set up your shiny servers in order to receive requests from your php scripts.
You should also enable shiny_secure-server to ensure that shiny server doesn’t block your requests when it doesn’t have the php_secure flag enabled.
If all else fails, you could try adding shiny-simple-schedulers as a package, which is a shiny package that doesn