CommunityRule/CommunityRuleBackend @ e08aeee91bd6a249d98b978e191a3542f20a2cd2

설명 없음

rota3015 e08aeee91b Updated dbConfig.js file to separate logic from email engine		7 달 전
config	e08aeee91b Updated dbConfig.js file to separate logic from email engine	7 달 전
controllers	56f4c8f07c Changed the email message	9 달 전
models	beb65349b6 first commit	1 년 전
routes	beb65349b6 first commit	1 년 전
README.md	897277ae13 Update 'README.md'	8 달 전
_site.zip	e9a136494d added zip file	9 달 전
app.js	beb65349b6 first commit	1 년 전
package-lock.json	c97ff664d5 integradted email engine	1 년 전
package.json	c97ff664d5 integradted email engine	1 년 전
run.sh	055fb04c13 Added run.sh	7 달 전

		
				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