Publishing a new community to the production server - kwantu/platformconfiguration GitHub Wiki

We recommend that you always create new communities on your staging server. This enables you to complete adoption of apps and other set up tasks without affecting your users. Once you are ready to publish your community to your production server, follow these steps:

  1. Create mysql entry in "communities" table.
INSERT INTO `community` (
`communityId`, 
`communityName`, 
`description`, 
`accessType`, 
`replicate`, 
`rcordSeq`, 
`webhookSeq`, 
`communityCode`) 
VALUES (
'b9341c47-ce52-4c62-8701-d5a0c7f2ecd4',
'IGC Partner A',
'IGC Partner A',
'1',
'1',
NULL,
NULL,
'829');
  1. Create entry in "user_roles_map" table for the new community to give access to Kwantu Administrator (user id 38)
INSERT INTO `user_roles_map` (
`userId`, 
`communityId`, 
`roleId`, 
`status`) 
VALUES(
'38',
'b9341c47-ce52-4c62-8701-d5a0c7f2ecd4',
'1',
'approved');
  1. Update user_table for user 38 and set buildAccess = 0 (This helps to give correct permissions on the database when user logins first time)
UPDATE user_ set buildAccess = 0 where userid = 38;
  1. Create the indexes for the community on the couchdb server. Run the create index service by passing parameter communityId=<NEW_COM_ID>
  2. Run publishCommunity to push configuration to production server from the staging server containing the initial configuration. See here for technical details
⚠️ **GitHub.com Fallback** ⚠️