jelster / gravitywell Goto Github PK

• Ensure DynamicTerrain extension is also updated from source

• Upgrade dependent modules along with Babylon

Move game from current azure storage static site to AS site

• Create AppService static site
• Use new ASP for independent scalability from LE.com site
• Custom domain: gravwell.liquidelectron.com

When the repos receives a commit push the following should happen:

• the web pack build should be executed

• tests (if any) should be executed

• artifacts from the build should be copied to a drop location

• artifacts should be copied from drop location to static website

• published artifacts should not be overwritten by new versions

It might make more sense to create an entirely new repos to contain that application

The gravity well website could use a landing page where visitors can

• View list of published versions

• Launch latest version

• Select a version to view/launch

As a contributor, I want to be able to quickly find my way around the GravWell code base so that I can make the most effective contribution to the project

Need to document some important things:

1. Local development build process

2. Any VSCode special setup or gotchas

3. WebPack integration, plugins, etc.

4. Custom ts.d files and content