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
I was going to enumerate two of these options. Currently, this can be solved with <meta> redirects, which are however very difficult to create in such a way that Frozen-Flask can collect them. Deploying for "real" would also solve this.
Well i was thinking we could teach Frozen-Flask to create those mate redirects when it sees a flask.redirect, but than again you would also need to feed it a route generator in order to be able to collect them. My opinion: Too much work, given the fact that we'll probably need to switch to dynamic website soon enough anyway.
Note: Even when we switch to something dynamic, I'd like to keep the Elsa-driven static site working for local development. But, URL stability won't matter too much there.
Activity
hroncok commentedon Jun 26, 2017
I see 3 options:
Sanqui commentedon Jun 26, 2017
I was going to enumerate two of these options. Currently, this can be solved with
<meta>redirects, which are however very difficult to create in such a way thatFrozen-Flaskcan collect them. Deploying for "real" would also solve this.hroncok commentedon Jun 26, 2017
Well i was thinking we could teach Frozen-Flask to create those mate redirects when it sees a
flask.redirect, but than again you would also need to feed it a route generator in order to be able to collect them. My opinion: Too much work, given the fact that we'll probably need to switch to dynamic website soon enough anyway.encukou commentedon Jun 27, 2017
Note: Even when we switch to something dynamic, I'd like to keep the Elsa-driven static site working for local development. But, URL stability won't matter too much there.