Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enable front end and backend Satellite UI code to be deployed independently #5843

Open
ferristocrat opened this issue May 2, 2023 · 3 comments
Open

Enable front end and backend Satellite UI code to be deployed independently #5843

ferristocrat opened this issue May 2, 2023 · 3 comments
Assignees
@cam-a
Milestone
CI/CD of Satellit...

Comments

@ferristocrat
Copy link

Motivation/Why?

  • Enable front end and backend Satellite UI code to be deployed independently for fastness and such

Acceptance Criteria

  • Both backend and UI containers still behind the same domain/load balancer (e.g. us1.storj.io); however, UI is served from one container, and a different container handles backend requests, e.g. metainfo/uplink, calls to /api endpoints from UI

Links

This infra PR is a proof-of-concept for what infrastructure change we would need to separate out a container for the UI from the main backend deployment. It can probably be used as a basis for a lot of this work.
@ferristocrat ferristocrat added the Enhancement New feature or request label May 2, 2023
@ferristocrat ferristocrat added this to the CI/CD Part 2 milestone May 2, 2023
@ferristocrat ferristocrat added Needs Grooming Needs Estimation Issue still needs story pointing and removed Enhancement New feature or request Needs Grooming labels May 2, 2023
@NiaStorj NiaStorj removed the Needs Estimation Issue still needs story pointing label May 7, 2023
@cam-a cam-a self-assigned this May 8, 2023
@cam-a cam-a added the Injection Added to sprint after sprint planning label May 8, 2023
@NiaStorj NiaStorj removed the Injection Added to sprint after sprint planning label May 9, 2023
@NiaStorj
Copy link

https://storj.slack.com/archives/C0490040EDR/p1685140337223719

@ferristocrat ferristocrat mentioned this issue Jun 13, 2023
Closed
@ferristocrat
Copy link
Author

Before deploying do the things in this issue: #5967

@storj-gerrit
Copy link

storj-gerrit bot commented Jun 16, 2023

Change satellite/console: optional separate web app server mentions this issue.

storjBuildBot pushed a commit that referenced this issue Jul 11, 2023
@cam-a
satellite/console: optional separate web app server
7e03ccf 
This change creates the ability to run a server separate from the
console web server to serve the front end app. You can run it with
`satellite run ui`. Since there are now potentially two servers instead
of one, the UI server has the option to act as a reverse proxy to the
api server for local development by setting `--console.address` to the
console backend address and `--console.backend-reverse-proxy` to the
console backend's http url. Also, a feature flag has been implemented
on the api server to retain the ability to serve the front end app. It
is toggled with `--console.frontend-enable`.

github issue: #5843

Change-Id: I0d30451a20636e3184110dbe28c8a2a8a9505804
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cam-a cam-a

Labels
None yet
Projects
None yet
Milestone
CI/CD of Satellite UI: Automated Prod...
Development

No branches or pull requests
3 participants
@ferristocrat @cam-a @NiaStorj