Settings and activity
3 results found
-
35 votes
We are actively working on this right now. Expect an update from us shortly on how you can try out this capability.
An error occurred while saving the comment 
Anonymous
supported this idea
·
-
3 votes
An error occurred while saving the comment Anonymous
commented
I think it is just because the exposed URLs (mine is:
https://5000-monospace-***-***-xxxx-xxxx.cluster-lknrrxxxxxx.cloudworkstations.dev/core/home
It shows a 'login with google' screen instead of serving my service.
It also requires a 'cookie' it seems, which is not possiblel from my service.An error occurred while saving the comment Anonymous
commented
I want to have a public API backend, that services (not a browser) can call. In this case. Google Workspace Add-ons. They do a request to my backend and expect a 200 response with a json object.
The documentation states:
We plan to simplify this in the near future, but for now, use the following workaround:
Projects that have an API backend can start their API services either manually in a terminal, or configure the startup command in the monospace.json file.
Open the port on which the API service runs to be accessible to your web frontend preview by running the following bash script in a terminal:export port=4000 #dont use restricted ports (8000, 9000-9002)
export API_SERVICE="https://$port-$WEB_HOST"
echo $API_SERVICEOpen the API_SERVICE URL above a new tab in your browser. This sets a required cookie through a redirect flow.
Your web app frontend can now access the API service at the fully qualified path.
But Google Add-ons are not able to do a redirect flow, besides, a lot of people get a google authentication issue as well (needs to be authenticated). Can I make a real public facing endpoint?
Anonymous
shared this idea
·
-
68 votesAnonymous
supported this idea
·
Yes, this is what I meant on my request. It is not public.