getPayload for Payload Cloud instead of Rest API?

face44

7 months ago

5

• 

  denolfe

  Payload Team

  7 months ago

  Interesting, I might be missing something in how you're using Payload, but how does hosting this in Payload Cloud change your usage?

  
  
  

  Now, we are migrating to Payload Cloud and realising that we'll have to rewrite all the services to use Rest APIs.
  

  
  

  Can you expand upon why you think that's the case?

• 

  Erielia

  7 months ago

  I had this same query, actually.

  
  
  

  I think the assumption is that the local API won’t work on payload cloud because payload is doing the work of connecting up to atlas mongo etc, while a front-end consumer of the payload cloud instance isn’t locally hosted alongside it, so presumably you need to use REST or GraphQL APIs to consume the data, for example in a nextjs app on vercel?

• 

  denolfe

  Payload Team

  7 months ago

  Hmm, we already expose the mongo connection string in the Cloud UI. I bet we could expose the payload secret as well. This would allow you to do

  payload.init

  from anywhere.

  
  
  

  Would that solve for this use-case?

• 

  face44

  7 months ago

  Hey,

  
  
  

  @Erielia summed it up pretty nicely.

  
  
  

  @denolfe

  
  

  I believe we'll be set if I am getting

  
  

  1. Mongo connection string

  
  

  2. Payload Secret

  
  

  3. Config? Can I get it?

• 

  denolfe

  Payload Team

  7 months ago

  Wherever you're performing your

  payload.init

  would need access to the config, but that's coming from your code repository in the first-place. It's not

  stored

  in Payload Cloud for retrieval or anything like that.