[Feature?]: Client rewrite of host to enable client and server deployments to different hosts (e.g. s3 for the client, ec2 for the server)

[greglearns]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Summary 💡

I'd like to serve the client code via S3/Cloudfront at www.example.com, and host the server code on an EC2 instance at api.example.com. Is that possible? We'd need to rewrite the client host for all API calls (and tRPC as well, but that's a different issue).

Examples 🌈

No response

Motivation 🔦

Serving the static assets via S3 would be nice, leaving the EC2 instance to only have to handle API requests instead of having to serve static assets.

[greglearns]

SOLUTION:
This is not related to SolidStart at all. Instead, set the URL using whatever request method you are currently using.

For example, if you are using:

• Fetch: set the URL in your fetch handler.
• Tanstack SolidQuery: just set the URL in your fetch code, or, create a default queryFn if you wanted to get fancy: https://tanstack.com/query/latest/docs/framework/react/guides/default-query-function?from=reactQueryV3 or https://tanstack.com/query/latest/docs/framework/solid/examples/default-query-function.
• tRPC: pass the base URL in createTRPCClient such as the below, or look at https://github.com/trpc/trpc/tree/next/examples/soa.

export const api = createTRPCClient<AppRouter>({
  links: [
    // identifies what url will handle trpc requests
    httpBatchLink({ url: `${getBaseUrl()}/api/trpc` }),
  ],
});

Closing this issue. Hopefully it will help someone who sees this in the future. Have a great day, from the past!