Configurable static assets path

[jabrks]

When using remix-serve, It's possible to specify a custom path to serve the build directory from with the publicPath property in remix.config.js.

remix/packages/remix-serve/index.ts

Lines 18 to 21 in 1bdeebf

	app.use(
	publicPath,
	express.static(assetsBuildDirectory, { immutable: true, maxAge: "1y" })
	);

However, no such option exists to do the same for the static files in the public directory.

remix/packages/remix-serve/index.ts

Line 23 in 1bdeebf

app.use(express.static("public", { maxAge: "1h" }));

It would be good to have the option to serve these files from a different path if desired.

[sergiodxa]

The files in the public directory are served from /, if you want to use another path create a folder inside the public folder, for example public/assets and they will be served from /assets

I’m not sure what more you need unless you want to be able to rename public to something else for another reason.

[jabrks]

The use case I had in mind was more along the lines of emulating a production environment in development.

When I deploy my app, I keep the contents of the public/ directory separate from the rest of the app. Any request to /assets is forwarded to the location of the static assets, and everything else is handled by my Remix request handler. I would like to be able to easily replicate this setup locally.

Right now, I've defined a splat route at /assets which proxies any request to /, but I'd prefer to be able to configure this in the dev server itself, hence this proposal.

[ryanflorence]

Use the express adapter and you get full control over your server. https://remix.run/docs/en/v1/other-api/adapter