CommunityRule/CommunityRuleBackend @ 513cf89e3a51a2b37461969f584d16f7fa8f69df

Bez popisu

1 Větve

rota3015 513cf89e3a Added email configuration file		před 7 měsíci
config	513cf89e3a Added email configuration file	před 7 měsíci
controllers	56f4c8f07c Changed the email message	před 9 měsíci
models	beb65349b6 first commit	před 1 rokem
routes	beb65349b6 first commit	před 1 rokem
README.md	897277ae13 Update 'README.md'	před 8 měsíci
_site.zip	e9a136494d added zip file	před 9 měsíci
app.js	beb65349b6 first commit	před 1 rokem
package-lock.json	c97ff664d5 integradted email engine	před 1 rokem
package.json	c97ff664d5 integradted email engine	před 1 rokem
run.sh	055fb04c13 Added run.sh	před 7 měsíci

		
				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