External Port Issue & Workaround

[vincanger]

Describe the bug
When using Wasp on Replit (https://replit.com/@vincanger/wasp-replit-template#.replit), we have to expose the client and server running on ports 3000 and 3001, to external ports so that Replit can host the app correctly. The default behavior is that anything exposed on localhost:3000 will be exposed externally at the default Replit url for that project. In this case, it is https://wasp-replit-template.vincanger.repl.co

Unfortunately, when the client running on localhost:3000 gets exposed at the default url and the server exposed externally at port 8099, the client often becomes unreachable after some time (see image above). This seems to be a bug on Replit's side, but we can work around it by exposing the client at an external port (e.g. 9000), and informing users to access their apps at this url, e.g. https://wasp-replit-template.vincanger.repl.co:9000

all the relevant files and config can be found here: https://github.com/wasp-lang/replit-template