found this but wasn't very helpful on what the key was https://www.graph.cool/forum/t/how-to-use-prisma-cli-to-login-in-ci-environment/2200

in graphcool framework the

platformToken

that you logged in with is in

~/.graphcoolrc

or in windows

C:\Users\your_user\.graphcoolrc

... I believe the same file but

.prismarc

exists

no such luck I found

cloudSessionKey

with in

.prisma/config.yml

but using it gives the same error

@thetrudel check this https://www.prisma.io/docs/reference/cli-command-reference/cloud/prisma-login-shaip5yaej

what if you open the link in your browser manually?

I think a good portion of the problem here is I am trying to play with this on AWS Cloud 9

@thetrudel, that's not needless to say 🙂 it's valuable feedback! what are the biggest painpoints there, besides the key issue you already mentioned?

It is more of an issue with Cloud 9's restrictions at least with using an EC2 instance. Last night I set up an environment using ssh and had more luck. Still haven't finished playing around with it but when I get some more time away from the day job I can try to gather some feedback for you.

that'd be awesome! I don't know a lot about Cloud 9, but maybe this Fargate tutorial is useful: https://blog.graph.cool/how-to-deploy-a-prisma-cluster-to-aws-fargate-using-docker-cloudformation-293aa8727b89

Yeh, I was looking at that new tutorial yesterday. I have actually had much success deploying to Kubernetes on GCloud and also on Digital Ocean. I also will be using Prisma cloud as well. Cloud9 is basically a browser IDE attached to a Linux server that acts like your local development machine. So the problems I was having using the EC2 instance was available ports and routing and what not. Moving to a DO droplet and attaching Cloud9 to it worked a little better however I have to figure out roles and user permissions. The basic idea is to have a cloud development environment. So the plan is to run the local Prisma docker containers on the droplet. Hope that clarifies some things.

@thetrudel Interesting to read. I remember when cloud9 first came out and thought it was a pretty cool. But now I'm more comfortable with node, shells, & programming in general & use VSC for performance/features/plugins. Then I sync those settings between OS/machines if necessary. Why do you use Cloud9? Is it out of habit or are there some benefits you don't get in a local IDE?

I actually develop locally. However sometimes I want to develop on a machine that I don’t want the local machine to have a copy of the code base. IP related. So it is more really a remote local development when I need it, 20% maybe

Cool makes sense. One more quick Q: Any reasoning for Cloud9 as opposed to renting & ssh into a cloud ubuntu desktop for remote dev? I think that would be my approach if I needed more RAM or couldn't solve some windows-specific problems (the latter happens pretty frequently testing new libraries in the node-sphere, thus the curiosity)

Well I kinda am doing that. I have Cloud9 setup with a Digital Ocean Ubuntu Droplet underneath. All Cloud 9 does is provide an editor/terminal in a browser window. The editor sees the Home directory and the files within and the terminal can have full sudo access to the droplet. Pretty much allowing you to do anything you can through ssh. So in the Prisma case you simply install Docker on the ubuntu box along with anything else you would for your local environment and you are off to the races. I could quite literally code on an iPad if I wanted. Got it set up on a $5 droplet available 24/7 to code or access via the terminal window. It is sorta like a backup when I can't use my personal machine for local development.