Usual process to change payload config / database schema in production

sssspray11 months ago

4

• 

  denolfe

  11 months ago

  You will need to explicitly run your migrations against the database. ie.

  payload migrate

  before running serve. This is not done automatically.

• 

  sssspray11 months ago

  @denolfe Yes, I tried that, but what I get is "No migration to run". Is it because I miss I step when changing the payload config ? Do I have to explicitly start a migration before doing a change in the payload config ?

  
  

  
  

  This part is unclear. I read the documentation carefully, but it doesn't provide much help 😦

  
  

  
  

  So to recap, the workflow I tried after @denolfe's hint is the following:

  
  

  1. Make changes to my Payload CMS configuration (e.g., add a field in a collection in

  payload.config.ts

  ).

  
  

  2. Commit and push these changes to my backend repository / Pull the changes on my live server.

  
  

  3. Run

  npm run build

  on my server.

  
  

  4. Run

  npm run payload migrate

  on my server to apply the changes to my database schema.

  -> But I get a "No migration to run" message
  

  5. Finally, run

  npm run serve

  on my server

  
  
  

  Is there something missing in this general workflow ? I even tried to empty the db to see if build/migrate would create the schema, but it didnt.

  
  
  

  I'm obviously missing something... At what point in the process is the schema supposed to be built in the db ?

  
• 

  denolfe

  11 months ago

  You are missing one part between 1 and 2. You need to run

  payload migrate:create

  to write the migration to a file.

  
  

  
  

  Check that file in. This will then be detected when you run migrate.

• 

  sssspray11 months ago

  @denolfe Great, thanks !