-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate deployment of Gateway frontend and backend #2032
Changes from 4 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,27 +15,16 @@ on: | |
- 'dev-testnet' | ||
- 'uat-testnet' | ||
- 'sepolia-testnet' | ||
|
||
jobs: | ||
build-and-deploy: | ||
runs-on: ubuntu-latest | ||
environment: | ||
name: ${{ github.event.inputs.testnet_type }} | ||
strategy: | ||
fail-fast: false | ||
matrix: | ||
include: | ||
- testnet_type: 'dev-testnet' | ||
GATEWAY_API_URL: 'https://dev-testnet.ten.xyz' | ||
- testnet_type: 'uat-testnet' | ||
GATEWAY_API_URL: 'https://uat-testnet.ten.xyz' | ||
- testnet_type: 'sepolia-testnet' | ||
GATEWAY_API_URL: 'https://testnet.ten.xyz' | ||
steps: | ||
- name: 'Print GitHub variables' | ||
run: | | ||
echo "Selected Testnet Type: ${{ matrix.testnet_type }}" | ||
echo "Gateway API URL: ${{ matrix.GATEWAY_API_URL }}" | ||
echo "Gateway API URL: ${{ vars.GATEWAY_URL }}" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. how is this differentiated for each env? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we have separate environments (https://github.com/ten-protocol/go-ten/settings/environments ) and for each environment we need |
||
|
||
- uses: actions/checkout@v4 | ||
|
||
|
@@ -46,7 +35,7 @@ jobs: | |
echo "BRANCH_NAME=${GITHUB_REF_NAME}" >> $GITHUB_ENV | ||
|
||
- name: 'Set up Docker' | ||
uses: docker/setup-buildx-action@v1 | ||
uses: docker/setup-buildx-action@v3.6.1 | ||
|
||
- name: 'Login to Azure docker registry' | ||
uses: azure/docker-login@v1 | ||
|
@@ -62,7 +51,7 @@ jobs: | |
|
||
- name: Build and Push Docker Image | ||
run: | | ||
DOCKER_BUILDKIT=1 docker build --build-arg GATEWAY_API_URL=${{ matrix.GATEWAY_API_URL }} -t ${{ vars.DOCKER_BUILD_TAG_GATEWAY_FE }} -f ./tools/walletextension/frontend/Dockerfile . | ||
DOCKER_BUILDKIT=1 docker build --build-arg GATEWAY_API_URL=${{ vars.GATEWAY_URL }} -t ${{ vars.DOCKER_BUILD_TAG_GATEWAY_FE }} -f ./tools/walletextension/frontend/Dockerfile . | ||
docker push ${{ vars.DOCKER_BUILD_TAG_GATEWAY_FE }} | ||
|
||
- name: "Deploy Gateway FE to Azure Container Instances" | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,56 +1,69 @@ | ||
# The Ten gateway | ||
|
||
See the documentation [here](https://docs.ten.xyz/wallet-extension/wallet-extension/). | ||
# Ten Gateway Documentation | ||
|
||
## Developer notes | ||
For a comprehensive overview, refer to the [official documentation](https://docs.ten.xyz/docs/tools-infrastructure/hosted-gateway). | ||
|
||
Running gateway frontend locally requires building static files first. | ||
To do that, run `npm run build` in `tools/walletextension/frontend` folder. | ||
## Running the Gateway Locally | ||
|
||
The precompiled binaries for macOS ARM64, macOS AMD64, Windows AMD64 and Linux AMD64 can be built by running the | ||
following commands from the `tools/walletextension/main` folder: | ||
### Backend | ||
|
||
``` | ||
To run the backend locally, first build it using the `go build` command. Navigate to the `tools/walletextension/main` folder and use the following commands to build for your respective operating system: | ||
|
||
```bash | ||
# macOS AMD64 | ||
env GOOS=darwin GOARCH=amd64 go build -o ../bin/wallet_extension_macos_amd64 . | ||
env GOOS=darwin GOARCH=arm64 go build -o ../bin/wallet_extension_macos_arm64 . | ||
|
||
# macOS ARM64 | ||
env GOOS=darwin GOARCH=arm64 go build -o ../bin/wallet_extension_macos_arm64 . | ||
|
||
# Windows AMD64 | ||
env GOOS=windows GOARCH=amd64 go build -o ../bin/wallet_extension_win_amd64.exe . | ||
|
||
# Linux AMD64 | ||
env GOOS=linux GOARCH=amd64 go build -o ../bin/wallet_extension_linux_amd64 . | ||
``` | ||
|
||
The binaries will be created in the `tools/walletextension/bin` folder. | ||
|
||
### Structure | ||
The binaries will be available in the `tools/walletextension/bin` directory. Run the compiled binary to start the backend. | ||
|
||
This package follows the same structure of `host` and `enclave`. | ||
### Frontend | ||
|
||
It uses a container to wrap the services that are required to allow the wallet extension to fulfill the business logic. | ||
Once the backend is running, navigate to the `tools/walletextension/frontend` directory and execute the following commands: | ||
|
||
### Running Wallet Extension with Docker | ||
```bash | ||
npm install | ||
npm run dev | ||
``` | ||
|
||
To build a docker image use docker build command. Please note that you need to run it from the root of the repository. | ||
To run the container you can use `./docker_run.sh`. You can add parameters to the script, and they are passed to the wallet extension | ||
(example: `-host=0.0.0.0` to be able to access wallet extension endpoints via localhost). | ||
The frontend will be accessible on `http://localhost:80`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this would need to be updated as well if you're happy to switch to 3000 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the problem is that gateway backend also runs on port 3000 (by default). |
||
|
||
## HTTP Endpoints | ||
|
||
### HTTP Endpoints | ||
Ten Gateway exposes several HTTP endpoints for interaction: | ||
|
||
For interacting with Ten Gateway, there are the following HTTP endpoints available: | ||
- **`GET /v1/join`** | ||
Generates and returns a `userID`, which needs to be added as a query parameter `u` in your Metamask (or another provider) URL to identify you. | ||
|
||
- `GET /v1/join` | ||
- **`POST /v1/authenticate?token=$EncryptionToken`** | ||
Submits a signed message in the format `Register <userID> for <account>`, proving ownership of the private keys for the account, and links that account with the `userID`. | ||
|
||
It generates and returns userID which needs to be added as a query parameter "u" to the URL in your Metamask | ||
(or another provider) as it identifies you. | ||
- **`GET /v1/query/address?token=$EncryptionToken&a=$Address`** | ||
Returns a JSON response indicating whether the address "a" is registered for the user "u". | ||
|
||
- `POST /v1/authenticate?token=$EncryptionToken` | ||
- **`POST /v1/revoke?token=$EncryptionToken`** | ||
Deletes the userId along with the associated authenticated viewing keys. | ||
|
||
With this endpoint, you submit a signed message in the format `Register <userID> for <account>` | ||
from that account which proves that you hold private keys for it, and it links that account with your userID. | ||
- **`GET /v1/health`** | ||
Returns a health status of the service. | ||
|
||
- `GET /v1/query/address?token=$EncryptionToken&a=$Address` | ||
- **`GET /v1/network-health`** | ||
Returns the health status of the node. | ||
|
||
This endpoint responds with a JSON of true or false if the address "a" is already registered for user "u" | ||
- **`GET /v1/network-config`** | ||
Returns the network configuration details. | ||
|
||
- **`GET /v1/version`** | ||
Returns the current version of the gateway | ||
|
||
- `POST "/v1/revoke?token=$EncryptionToken"` | ||
- **`GET /v1/getmessage`** | ||
Generates and returns a message for the user to sign based on the provided encryption token. | ||
|
||
When this endpoint is triggered, the userId with the authenticated viewing keys should be deleted. |
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,41 @@ | ||
# Use an official Node.js 22 as a parent image | ||
FROM node:22-alpine | ||
# Use an official Node.js LTS version as a base image | ||
FROM node:20-alpine AS base | ||
|
||
WORKDIR /usr/src/app | ||
|
||
# ARG for build-time variable (GATEWAY_API_URL) | ||
ARG GATEWAY_API_URL | ||
|
||
# ENV for URL to be used in the app | ||
ENV NEXT_PUBLIC_API_GATEWAY_URL=${GATEWAY_API_URL} | ||
ENV PORT=80 | ||
|
||
# Copy package.json and package-lock.json (or yarn.lock) into the container | ||
COPY package*.json ./ | ||
# Set the working directory | ||
WORKDIR /usr/src/app | ||
|
||
RUN npm install | ||
COPY . . | ||
# Copy the necessary files to the working directory | ||
COPY tools/walletextension/frontend/ . | ||
|
||
# Install dependencies | ||
RUN npm ci | ||
|
||
# Build the Next.js app | ||
RUN npm run build | ||
|
||
# Reduce the size of the final image by using a lighter base image | ||
FROM node:20-alpine AS runner | ||
|
||
# Set the working directory | ||
WORKDIR /usr/src/app | ||
|
||
# Copy only the necessary files from the build stage | ||
COPY --from=base /usr/src/app/.next ./.next | ||
COPY --from=base /usr/src/app/public ./public | ||
COPY --from=base /usr/src/app/package*.json ./ | ||
|
||
# Install production dependencies | ||
RUN npm ci --production | ||
|
||
|
||
# Set the environment variables | ||
ENV PORT=80 | ||
|
||
# Expose the port | ||
EXPOSE 80 | ||
CMD ["npm", "start"] | ||
|
||
# Start the application | ||
CMD ["npm", "start"] |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,9 @@ | ||
/** @type {import('next').NextConfig} */ | ||
const nextConfig = { | ||
reactStrictMode: true, | ||
output: "export", | ||
// distDir should be "../api/static" in production but .next in development | ||
distDir: process.env.NODE_ENV === "development" ? ".next" : "../api/static", | ||
images: { | ||
unoptimized: true, | ||
}, | ||
// base path for static files should be "" in development but "/static" in production | ||
basePath: process.env.NODE_ENV === "development" ? "" : "/static", | ||
}; | ||
|
||
module.exports = nextConfig; |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,7 +3,7 @@ | |
"version": "0.1.0", | ||
"private": true, | ||
"scripts": { | ||
"dev": "next dev", | ||
"dev": "next dev -p 80", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and this |
||
"build": "next build", | ||
"start": "next start", | ||
"lint": "next lint" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we stick to the usual FE convention of 3000 for the FE?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this workflow is for the backend gateway (API)