General

[JudeDavis1]

General discussion about features and more.

[j-koziel]

So I had to move morgan to a normal dependency because google cloud doesn't seem to install the dev dependencies causing it to crash as it can't find the module when we are importing it in the app file. For now the workaround is to save it as a normal dependency but hopefully there will be another way

[JudeDavis1]

@j-koziel When our code is deployed to the cloud, the remote server should not touch dev dependencies, or any other dev code. In an ideal scenario, the cloud server ONLY touches production code. Ideally we can make a branch called 'stable' and 'production' can contain the build. I think this will make it safer for deployment.

[j-koziel]

could you please explain what the difference between stable and production would be?

[JudeDavis1]

stable code is code that good to deploy. I.e fixed bugs, functional etc. It's basically a release.

production code is just the code that actually deployed, in our case, the build folder. I can explain better tmrw if you like.

[j-koziel]

Another thing I wanted to introduce is 2 different start scripts. Again this is mainly because we use nodemon as our start script and it's also a dev dependency which means google does not install it. Therefore, I think it would be beneficial to have a start:dev and start:prod sccript; the prod running node and dev running nodemon.

[JudeDavis1]

That's a good idea.

[j-koziel]

It doesn't look like google let's you run your own start script it just looks for the "start" in the package file so it might get confused between start:dev and prod

[j-koziel]

I'm going to test this theory when i have time and see what happens