At the moment, when server receives a request for repo that is already destroyed (hence no PreviewApps table in dynamodb) or a user profile that does not exist anymore in config file for AWS(this should not technically happen), the error needs to be caught. In the front end, apps should not really be pulled unless the status is meant to be active;
needs to add command so server and client runs at the same time
needs to connect bubble framework with bubble dashboard, so when the command is run, npm start server and client will spin up
can potentially add bubble teardown button for the destroyed repo app page
Things that to be fixed and polished:
appsshould not really be pulled unless thestatusis meant to beactive;npm startserver and client will spin upbubble teardownbutton for the destroyed repo app page