Closed epicfaace closed 4 years ago
I think the calendar is broken e.g. if you go to http://localhost:3000/1895/01/ then I get an unhandled runtime error
@ufxela hmm it's working for me -- can you try doing yarn
and try again?
We still have the issue where going directly to https://d148m2cwwi25lc.cloudfront.net/calendar and https://d148m2cwwi25lc.cloudfront.net/acknowledgements doesn't work. No idea why this is happening
We still have the issue where going directly to https://d148m2cwwi25lc.cloudfront.net/calendar and https://d148m2cwwi25lc.cloudfront.net/acknowledgements doesn't work. No idea why this is happening
huh weird. also https://d148m2cwwi25lc.cloudfront.net/acknowledgements works for me. Calendar is broken though.
also https://d148m2cwwi25lc.cloudfront.net/acknowledgements works for me.
working for me too now!
oddly, even though month pages don't work on cloudfront, they do work when running locally. Huh.
I do get this warning when running locally and going to a month page
Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
* Move code from componentWillMount to componentDidMount (preferred in most cases) or the constructor.
Please update the following components: Uncontrolled(Calendar)
in Uncontrolled(Calendar)
in ForwardRef (at CalendarView.jsx:96)
in div (at CalendarView.jsx:95)
in div (at CalendarView.jsx:74)
in CalendarView
in withRouter(CalendarView) (at _app.jsx:46)
in div (at _app.jsx:45)
in div
in Div100vh (at _app.jsx:33)
in App
in Unknown
in Context.Provider
in Context.Provider
in Context.Provider
in AppContainer
updated big calendar to newer version, so I no longer get that warning. Maybe that will fix cloudfront? idk
Reasons for making this change
Faster on the client side to use SSR pages. Also, then we can deploy to AWS using the same configuration we're using for stanforddaily.com
Run
yarn dev
to start, andyarn deploy
to deploy.Deployed at: https://d148m2cwwi25lc.cloudfront.net/