Closed emw8105 closed 1 week ago
When deploying, make sure to fix route directing / api calls for each so that the new route points to wherever the endpoint it's hosted on is, including the redirect uri within the spotify app
35ba09ec673bf62ee6967c7e59a0021d9e0021ef: Server fully deployed to EC2 with AWS services to support both new and existing features, localhost client requests to EC2 endpoint, still need to deploy frontend
Repo is deployed to Vercel, but currently having issues with requests between the client and server, see here: https://github.com/emw8105/Wallify/issues/12 Once this issue is solved, will need to redirect request endpoints to reflect the new domain name (i.e. handlers.go redirecting the client to localhost:3000 after the callback function is completed)
App is fully deployed across several services, but chrome and edge have weird issues with the spotify developer portal at the moment, and that seems to be reflected in some user's spotify login abilities. Not directly related to the app as it affects me using the developer portal itself, so we're just gonna hope it goes away and if not I'll look up some common fixes
Due to the split-hosted nature of the project and the constant new ideas for optimization and continued development, deployment has been something pushed off for later. However, it would be fun to put it out there, so when it's ready it should be a goal to shoot for.