brumbrum_brum Comments - Answer Overflow

brumbrum_brum

Explore posts from servers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

Thank you so much! It seems like most areas around the world are starting to propogate my changes, and I can reach it from my PC.

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

But in Route 53 I already have some auto-generated records for nameservers in my hosted zone. Should I remove those from route 53, or should I just leave them?

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

Yea I think you are right, just found and article and video doing the same for Cloudflare specifically. I have changed the settings, so I will just wait and see. Thank you!

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

And also, when using DNS lookup tools, should I be able to see the CNAME record? Currently there are no records.

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

Just to clarify, so I am not waiting for an invalid DNS propagation. I can only create an DNS record in AWS of type A, if I want to connect it to my gateway. Should I still just use the value for a CF CNAME record, from the aws A type value?

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

Ah okay, thank you

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

What "old record" are you talking about? I am not super well versed in all this domain and dns stuff.

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/11/2024 in #general-help

AWS Route 53 Alias DNS

And then just use the same value? I have tried it, but it does not seem to work. Since I just did it about 30 minutes ago, the changes might not have propogated yet?

19 replies

CDCloudflare Developers

•Created by brumbrum_brum on 9/7/2024 in #pages-help

ENV variables with wrangler pages CLI (VITE REACT)

So I tried those solution but they did not work. Because I was building my React app with Vite, the ENV variables were taken from the .env file. I ended up manually creating an .env file in my github action, like this:

- name: Create .env file
        working-directory: ./apps/frontend
        run: |
          echo 'VITE_VARIABLE="${{ secrets.VALUE}}"' >> .env
          echo 'VITE_VARIABLE2="${{ secrets.VALUE2}}"' >> .env

- name: Create .env file
        working-directory: ./apps/frontend
        run: |
          echo 'VITE_VARIABLE="${{ secrets.VALUE}}"' >> .env
          echo 'VITE_VARIABLE2="${{ secrets.VALUE2}}"' >> .env