Home Explore Help
Register Sign In
CommunityRule
/
CommunityRuleBackend
2
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki

No Description

Tree: e08aeee91b
Branches Tags
CommunityRuleBa...
ZIP TAR.GZ
rota3015 e08aeee91b Updated dbConfig.js file to separate logic from email engine 7 months ago
config e08aeee91b Updated dbConfig.js file to separate logic from email engine 7 months ago
controllers 56f4c8f07c Changed the email message 9 months ago
models beb65349b6 first commit 1 year ago
routes beb65349b6 first commit 1 year ago
README.md 897277ae13 Update 'README.md' 8 months ago
_site.zip e9a136494d added zip file 9 months ago
app.js beb65349b6 first commit 1 year ago
package-lock.json c97ff664d5 integradted email engine 1 year ago
package.json c97ff664d5 integradted email engine 1 year ago
run.sh 055fb04c13 Added run.sh 7 months ago

README.md

Backend

  • Our code is present at /app/data/public/communityRuleBackend.
  • Our backend is being running on port 3000.
  • Internally, there is one run.sh which is responsible to run any script on start of the server. We are running another run.sh which is in our public/communityRuleBackend/run.sh which is kind of for loop which will keep on running and check every 30 mins if our backend is working or not if it is not working it will start the backend.
  • Our database is also present in the same cloudrun environment
  • We are using email engine provided by cloudrun
  • Details regarding database and email is present in code dbConfig and emailConfig