You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bit of an anti-pattern to use express for a lambda function
currently http://peterportal.org doesn't work since API gateways only allow TLS. this issue should be avoidable under different infrastructure using Next, there might be other ways to solve this though (if we can put the api gateway behind a cloudfront distribution). (Infrastructure changes #442)
cons:
new technology, re-learning required for members
additional consideration needed to be taken with client/server components
different routing
etc.
need to look into some other way of handling authentication, sessions (NextAuth?)
current setup uses passport/session middleware for Express and it persists between lambda deployments since the session is stored in mongo
The text was updated successfully, but these errors were encountered:
Should we consider migrating to Next?
pros:
currently http://peterportal.org doesn't work since API gateways only allow TLS. this issue should be avoidable under different infrastructure using Next, there might be other ways to solve this though (if we can put the api gateway behind a cloudfront distribution).(Infrastructure changes #442)cons:
The text was updated successfully, but these errors were encountered: