-
Notifications
You must be signed in to change notification settings - Fork 27
refactor deploy html #362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor deploy html #362
Conversation
- make_html_bundle - make_html_bundle_content
010c686 to
32bd359
Compare
|
fixes #361 |
|
I still get a 404 when deploying static content with an index not named I deployed with and |
|
also, fixes #359 |
|
Can deploy and render... single html file: deploy by directory, no entrypoint
single html file deploy by directory with entrypoint single html file: deploy by filename
single html file: deploy by filename with entrypoint
multi html deploy: deploy by directory, no entrypoint
multi html deploy: deploy by file
|
|
When specifying an entrypoint that doesn't exist we don't catch the error and give a reasonable response, instead we throw a NoneType Err: In this example the |
|
When specifying two files in an html deployment, from outside the directory, we state: With this file structure: From outside the directory: When specifying two files in an html deployment, from inside the directory, we state: The same error is presented, even when providing the full path of the second.html file as the error suggests: |
fixed by f5a2146
fixed by 2f8703a |
These fixes look good. |
|
Windows testing. When multiple files are in the target directory it fails with this error: Directory structure: |
|
When specifying an entrypoint where multiple html files exist...
Directory structure:
|
8e1f533 to
dc011c0
Compare
remove create_abspath_list
dc011c0 to
0415875
Compare
fixed by 0415875
This depends on where you are deploying the files. If you are outside the folder, you have to give it the full path.
fixed by 0415875 |
|
It looks like this part is still broken:
|
The full path has to be specified for the entrypoint if you are outside the folder. So in this case: The other way is to do relative deploy, like so: |
4b4b312 to
43b49df
Compare
I realize it works as expected when you're in the directory you're trying to deploy. However that's not the way other content-types work. Are we fine with deviating away from how other deployment types work for html using We'll at least have to document around that. |
7b5c7db to
2740862
Compare
Added documentation on the deploy html behavior in the changelog Let me know if there's anything that's missed. |
2740862 to
82010ce
Compare
|
Testing on Windows is complete. I think we're good to merge 👍 |
82010ce to
07d182c
Compare

Description
deploy htmlbased on the new Manifest and Bundle classesdeploy html