revert FE to port 80

This makes testing containerization easier

Author: topocount

SETUP.md

@@ -22,16 +22,12 @@ Run the frontend.
 
 ```sh
 npm i
-cd apps/frontend && npm run dev
+cd apps/frontend && sudo npm run dev
 ```
 
-if you want to hack on the telegram login flow, you'll need to proxy port 80 to the development port
+The reason we're running sudo here is because the Telegram login widget needs access to port 80 to work. This is definitely not ideal and something we should fix so contributors don't need to run sudo.
 
-```sh
-brew install socat
-sudo socat TCP-LISTEN:80,fork TCP:localhost:8080
-```
-`sudo` is needed to access port 80.
+`sudo` is only needed to access port 80.
 
 Navigate to [127.0.0.1](http://127.0.0.1/)
 

apps/frontend/src/pages/NewCustomGroup/components/TelegramBotSetup.tsx

@@ -18,7 +18,7 @@ export const TelegramBotSetup = () => {
 
   return (
     <>
-      {/* In local dev, you need to set bot's domain to 127.0.0.1:80 for FE button to work
+      {/* In local dev, you need to set bot's domain to 127.0.0.1 for FE button to work
       But the backend validation will fail if the bot's domain is not the same as the one set in the backend
       */}
       {!telegramIdentity && <TelegramLogin />}

apps/frontend/vite.config.ts

@@ -24,7 +24,7 @@ export default defineConfig(({ mode }) => {
     },
     server: {
       host: "127.0.0.1",
-      port: 8080,
+      port: 80,
       proxy: {
         "/api": {
           target: env.VITE_LOCAL_BACKEND_URL,

docker-compose.yaml

@@ -29,7 +29,7 @@ services:
       - "3000:3000"
     environment:
       - MODE=development
-      - LOCAL_URL=http:/127.0.0.1
+      - LOCAL_URL=http://127.0.0.1
       - PORT_FORWARDING_ADDRESS
       ## Alchemy
       - ALCHEMY_API_KEY