render.md - is-a-dev-docs - is-a.dev Documentation

render.md (1417B)
      1 ---
      2 order: 1100
      3 icon: /media/render.svg
      4 label: Render
      5 tags: guides
      6 ---
      7 
      8 # Setting up Render with an is-a.dev Subdomain
      9 
     10 This guide will walk you through the process of setting up a Render deployment and pointing your is-a.dev subdomain towards it.
     11 
     12 ## Creating a Render Service
     13 
     14 First, create a service on Render. Follow the instructions in the [Render Documentation](https://docs.render.com/).
     15 
     16 ### Creating the Domain File
     17 
     18 Create a JSON file inside the `domains` directory (`domains/subdomain.json`) with the following content and submit a pull request:
     19 
     20 ```json
     21 {
     22     "owner": {
     23         "username": "your-github-username"
     24     },
     25     "records": {
     26         "A": ["216.24.57.1"]
     27     }
     28 }
     29 ```
     30 
     31 **Note:** Don't forget to provide a preview of your website in your pull request.
     32 
     33 ## Configuring Render
     34 
     35 - After your pull request is merged, you may need to configure your Render service to use the new subdomain. Go to your Render service's dashboard.
     36 - Navigate to **Settings > Custom Domains** and add `subdomain.is-a.dev` in the given field.
     37 - Render will provide a verification step, usually requiring you to add a DNS record. This step should be skipped if your subdomain is already pointing to Render's IP address (`216.24.57.1`).
     38 
     39 ### Final Steps
     40 
     41 - Wait for the DNS changes to propagate. This can take from a few minutes to a couple of hours.
     42 - Your Render service should now be accessible at `subdomain.is-a.dev`.