Add redirect from old demo URL to new URL

[pshycodr]

issue: #208

Add redirection rule to fly-client.toml to redirect traffic from https://saas-template-gpt-client.fly.dev/ to https://opensaas.sh.

• Add [http_service.http_options.redirects] section to handle redirection.
• Add rule to redirect all traffic from https://saas-template-gpt-client.fly.dev/ to https://opensaas.sh.

[vincanger]

one for you @infomiho

[infomiho]

I'm not sure if editing the opensaas.sh client TOML file will add the redirect to the old client. We should probably edit the old demo client TOML file. @vincanger is it in the old saas template repo?

[pshycodr]

@infomiho @vincanger Thanks for the feedback! To confirm, should I add the redirect rule to the old demo client’s fly-client.toml in the SaaS template repo? Or is there another preferred way to handle this? Let me know how you'd like me to proceed!

[infomiho]

@pshycodr Yes, that would be the right course of action. I can see in the old template repo we don't have the TOML files for deployment, so you might not be able to do it.

@vincanger do you have the TOML files locally or?

[pshycodr]

@infomiho @vincanger Got it! If the TOML files aren’t in the old template repo, let me know where I can find them or if there’s another way to set up the redirect. Happy to proceed once I have the right files!

[vincanger]

@infomiho I can't seem to find the old toml files. What could we do instead?

[pshycodr]

Since you can't find the old fly.toml files, here are a few possible approaches you could consider:

1. If Fly.io allows changes via the dashboard, you can try updating the settings there.
2. Try to fetch the config with flyctl config save. This will generate the fly.toml file with the current config. Then update the redirect rules from there directly.
3. If you have access to the website's code, we can implement a server-side redirect.