Hi @tarrencev ! We have an article that describes how to use GKE here: https://adaptjs.org/blog/2020/01/10/simple-hosting-react-app-on-google-cloud
Let me know if that's not quite what you're looking for and we can help out.
@mterrel i want to enable https for local development. is there a way to setup nginx to support this?
Yes, there is logging, although it's not as great as we'd eventually like it to be. Currently, we use the Node.js debug module with the prefix
adapt:. To see Docker related stuff during build:
DEBUG=adapt:cloud:docker* adapt run ...
That's the most verbose version of docker logging. Once you see the output, you can change the
DEBUG= to show more or less stuff.
If you really want a lot of output, use
DEBUG=adapt*
There isn't an existing example of setting up Nginx with HTTPS, but there definitely should be! If you'd like to contribute an example setup, that would be awesome. Either way though, we can help you get it set up if you'd like. There are Nginx components that should be a good starting point.
But should be able to answer questions in the meantime too
Ah, there's a UrlRouter component for that. The Nginx implementation of that component is here. And the getting started guide uses that component to route traffic for
/api to an API backend service and routes everything else to a static HTTP server (also Nginx).
To create a new adapt project that's a simple starting point that includes the UrlRouter:
adapt new hello-react-node-postgres ./some_dir
To see a slightly more full featured demo with it:
adapt new moviedb-react-node ./some_other_dir
<NodeService port={80} handle={api} srcDir="../backend" />
<NodeService port={90} handle={api2} srcDir="../backend" />
would that create separate containers for each port?
Hold on, lemme look at it for a sec...
const hostname = callInstanceMethod(api, undefined, "hostname");
...
<UrlRouter port={8080} routes={[
{ path: "/api", endpoint: `http://${hostname}:80` },
{ path: "/api2", endpoint: `http://${hostname}:90` }
]} />
I think that will work ok for local docker deploy. But in order to make it work in GKE, you'd need to copy and modify NodeService to allow it to take multiple ports to listen on so it correctly creates a NetworkService that corresponds to each of those also.
And maybe the dual NodeService can work for you in the short term?
I'm getting a compile error when trying to run yarn build in the cloud/ directory:
~/Projects/Adapt/adapt/cloud$ yarn build
yarn run v1.19.1
$ tsc -p tsconfig.json
src/aws/aws-sdk.ts:17:10 - error TS2305: Module '"../../../node_modules/@adpt/utils/dist/src"' has no exported member 'ciMaybeCreateLogger'.
17 import { ciMaybeCreateLogger, ciReportEnabled, makeRetryDelay } from "@adpt/utils";
~~~~~~~~~~~~~~~~~~~
src/aws/aws-sdk.ts:17:31 - error TS2305: Module '"../../../node_modules/@adpt/utils/dist/src"' has no exported member 'ciReportEnabled'.
17 import { ciMaybeCreateLogger, ciReportEnabled, makeRetryDelay } from "@adpt/utils";
~~~~~~~~~~~~~~~
src/aws/aws-sdk.ts:17:48 - error TS2305: Module '"../../../node_modules/@adpt/utils/dist/src"' has no exported member 'makeRetryDelay'.
17 import { ciMaybeCreateLogger, ciReportEnabled, makeRetryDelay } from "@adpt/utils";
~~~~~~~~~~~~~~
Found 6 errors.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.This is off of master at cb497355477d9bf0887555fd0110854fa54d580c plus some changes to add some code into cloud/aws/.
Hi @tdyas , There are two things that are the most likely causes. The first one may be environment, tool, or dependency related and can be diagnosed by changing to the top level
adapt repo directory and trying make cleaner; make build. That will do a complete cleanup, then build everything from scratch, using the containerized dev environment instead of your local system's tools and environment. Generally speaking, you shouldn't build or test using your system's native tools and environment, but rather use the containerized version of those, which can be found in the bin directory at the top level of the adapt repo. So instead of running yarn build in the cloud directory, you'd run ../bin/yarn build. And by using make instead of directly calling yarn, that ensures that dependencies have definitely been correctly (re-)built.
If that doesn't build successfully, can you stash your
cloud/aws changes and try make cleaner; make build again? Then, let me know the results and I can help you troubleshoot more from there.
make cleaner && make build fails due to no access to adapt-web repo:git clone git@gitlab.com:unboundedsystems/adapt-web.git web
Cloning into 'web'...
Warning: Permanently added the ECDSA host key for IP address '172.65.251.78' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
/src/config/build_support/web.mk:30: recipe for target 'web/.git' failed
make: *** [web/.git] Error 128
make: *** [/home/tdyas/Projects/Adapt/adapt/config/build_support/dockerize.mk:36: .DOCKER_MAKE_DONE] Error 2
Oh, I may have spoken too soon. It may be a permissions problem. Investigating and fixing...
Ok, adapt-web should be public now. Try
make build again. It is somewhat possible that it still gives a permissions error in that context though. If you still see the permissions error, try the manual clone as suggested above. And either way, let me know how that goes and I'll file a bug if needed.
I created unboundedsystems/adapt#11
