WebComponent now supports Resources, but it would be better if FuzeWorks didn't have to serve static files at all. Resources are a good fallback, but FuzeWorks should really just write a .htaccess file or provide nginx directives to be installed.
A HTTP Server Config Writer class needs to be implemented which should be run every time a resource is added, removed or modified. This will allow the developer to severely lessen the load on FuzeWorks for serving static content.
``WebComponent`` now supports Resources, but it would be better if FuzeWorks didn't have to serve static files at all. Resources are a good fallback, but FuzeWorks should really just write a ``.htaccess`` file or provide ``nginx directives`` to be installed.
A ``HTTP Server Config Writer`` class needs to be implemented which should be run every time a resource is added, removed or modified. This will allow the developer to severely lessen the load on FuzeWorks for serving static content.
WebComponent
now supports Resources, but it would be better if FuzeWorks didn't have to serve static files at all. Resources are a good fallback, but FuzeWorks should really just write a.htaccess
file or providenginx directives
to be installed.A
HTTP Server Config Writer
class needs to be implemented which should be run every time a resource is added, removed or modified. This will allow the developer to severely lessen the load on FuzeWorks for serving static content.