-
Notifications
You must be signed in to change notification settings - Fork 98
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
Web deploy prerequisites #1851
Web deploy prerequisites #1851
Conversation
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Codecov Report
@@ Coverage Diff @@
## develop #1851 +/- ##
===========================================
+ Coverage 95% 95.03% +0.02%
===========================================
Files 119 119
Lines 2565 2558 -7
Branches 120 120
===========================================
- Hits 2437 2431 -6
+ Misses 118 117 -1
Partials 10 10
|
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
…tes' into sabau/web/1833-deploy-prerequisites
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
…tes' into sabau/web/1833-deploy-prerequisites
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com> # Conflicts: # .circleci/config.yml # app/src/renderer/connectors/node.js # app/src/renderer/main.js # package.json # test/unit/specs/connectors/node.spec.js # webpack.renderer.config.js # yarn.lock
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
…loy-prerequisites
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
The coverage is a bit funny, I think it says that is not covered anymore since when I removed he side effect (main() was called for real once the file was imported and it was touching this function but was not tested for real) |
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Co-Authored-By: sabau <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
@@ -0,0 +1,67 @@ | |||
#!/bin/bash |
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.
do we need to include .aws
files? @cosmos/sre ?
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.
those are used by the current (temporary) node setup on EC2, until the real network boot on merge is ready
|
||
// this will pass the state to Sentry when errors are sent. | ||
// this would also sent passwords... | ||
// Sentry.configureScope(scope => { |
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.
commented out?
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.
left in as a warning to not do this. see the comment
Re coverage: I think the router setup could be escaped via |
* custom image for voyager build / AWS deployment
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
…docker image and alias, we use docker-deploy instead Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
Signed-off-by: Karoly Albert Szabo <szabo.karoly.a@gmail.com>
@@ -72,4 +71,95 @@ describe(`App Start`, () => { | |||
expect(startApp).toHaveBeenCalled() | |||
expect(startApp.mock.calls[0][0]).toHaveProperty(`x`, 1) | |||
}) | |||
|
|||
it(`Check the calls on VUE`, async () => { |
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.
I would have maybe just called the function and checked if it doesn't throw.
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.
yeah I tried to test the real call but was taking a weird path to mock them, so I just counted the number of calls
Co-Authored-By: sabau <szabo.karoly.a@gmail.com>
Closes #1833
Description:
demo
Deployment of nodes followup (I won't do all this in the first PR, but we know it's possible and we can specify those details to the SRE team next call)
My plan is to have two node types:
gaia in a Docker exposing RPC port
gaiacli in another Docker, exposing the rest server, but pointing to the first machine of type
gaia
Eventually an nginx or APIGateway, the chapest solution will win 🎉
Is possible, BUT the genesis file should be on both node types
In this way we will be able to spin up gaia nodes as hell and just one gaiacli node pointing to (let's say) the first gaia node, so the gaiacli node can scaleup indipendently if he receives burst of requests, but the real nodes are always the same
gaiacli [command] --node=IP:PORT
❤️ Thank you!
CHANGELOG.md
with issue # and GitHub usernameFiles changed
in the github PR explorer