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
Hiya, I would like to be able to deploy files in a certain order, specifically the index.html file after all the other assets have been copied over. This will decrease downtime, as all the assets will be resolvable as soon as index.html is served.
I've worked around this by deploying using these 2 commands:
@stefan-lz I don't think we currently support ordering for the file uploads but that doesn't mean we can't. Your workaround seems pretty clever and functional to me. But I think we'd be happy to accept something that simplifies the process.
Hiya, I would like to be able to deploy files in a certain order, specifically the
index.html
file after all the other assets have been copied over. This will decrease downtime, as all the assets will be resolvable as soon asindex.html
is served.I've worked around this by deploying using these 2 commands:
with this config:
Am I missing an easier solution, or could this be better supported in finch?
The text was updated successfully, but these errors were encountered: