# Hooking up local FlyteConsole to remote backend (FlyteAdmin)

## What are we trying to do
FlyteConsole runs a nodeJS app that makes XHTTPRequests to FlyteAdmin Service. In production, the service as well as FlyteConsole usually run on the same host.

## Steps to make it work

1. Run the following command to tell flyte console to communicate with this domain for XHTTPRequests

   export ADMIN_API_URL=https://demo.nuclyde.io

1. Run these commands to update deps and start FlyteConsole

   yarn
   yarn start

---
**NOTE**

Your console is now accessible on http://localhost:3000 but that's not useful because it breaks Cross-Site-Scripting policies making the browser block certain features we need to make these requests work.

---

1. Edit your hosts file

   sudo vim /etc/hosts

Add the following line:
``127.0.0.1 localhost.demo.nuclyde.io``

---
**NOTE**

Your url must be a subdomain of the domain you configured in step 1. This is required to tell your browser it's ok to send the cookies on your XHTTPRequests

---

1. Install [this plugin](https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) to bypass CORS requirements

1. Open the plugin page and click on the logo to enable it.

You should be able to go to your local deployment and access remote data: http://localhost.demo.nuclyde.io:3000