CommunityRule/CommunityRuleBackend @ 769bdc4e2402d31622dbbf87aa48416fca4acd36

Aucune description

rota3015 769bdc4e24 Created ReadMe		il y a 8 mois
config	c97ff664d5 integradted email engine	il y a 1 an
controllers	56f4c8f07c Changed the email message	il y a 9 mois
models	beb65349b6 first commit	il y a 1 an
routes	beb65349b6 first commit	il y a 1 an
README.md	769bdc4e24 Created ReadMe	il y a 8 mois
_site.zip	e9a136494d added zip file	il y a 9 mois
app.js	beb65349b6 first commit	il y a 1 an
package-lock.json	c97ff664d5 integradted email engine	il y a 1 an
package.json	c97ff664d5 integradted email engine	il y a 1 an

		
				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 backend is also present in the same cloudrun environment.