-
Notifications
You must be signed in to change notification settings - Fork 504
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
Why not delegate publishing completely to quarto publishing framework? #1066
Comments
Can you try putting |
Also read these docs https://nbdev.fast.ai/explanations/docs.html#deploying-your-docs-on-other-platforms can you make this work locally? If so, you should be able to do the same in GitHub Actions |
My current workflow is following :
Nevertheless, my reason for the request is to avoid an additional render done in the nbdev_docs command and then again in the quarto-actions when following this workflow. Also a possible use case with multiple user setups / "Knowledge repo" is to have a different deployment target/ URL for users with different roles/ permissions which I am unable to achieve cleanly. I raised a ticket on quarto forums quarto-dev/quarto-actions#44 (comment) and they mentioned something like profiles that could be in work for quarto publish. |
Did you try this?
|
No, not yet. Let me try this today and report back |
Version 2.3.0
Request for enhancement
Why not delegate publishing completely to quarto publishing framework?
With the introduction of _proc in version 2.3.0 , nbdev resolves a few issues around publishing. But it still doesn't completely capitalize _quarto publishing functionality.
Let me try to explain
When I run the nbdev_preview command a _docs folder is generated in the _proc directory. Looking at the source code I believe same/similar _docs folder is generated by the nbdev_docs command at the root directory.
My thought process is following
(In fact, default deployment to GitHub pages can be already configured for _publish.yml while generating _proc folder using nbdev_prepare but can be modified by a user on demand based on a case-by-case basis.)
The below setup for deploy has not worked ( might be an issue with quarto-action) - with various combinations of path[ _proc, ./_proc] or putting _publish.yml in multiple places ( _proc dir, root dir, both, etc..)
Note : - I can run quarto publish netlify locally (it's just that quarto action is failing for some reason)
Failing with following message :-
No _publish.yml file available (_publish.yml specifying a destination required for non-interactive publish)
I am using the following to achieve netlify deployment which solves what I want to achieve for now. However, it would be much better if we can link to publishing framework directly from quarto. This way it would be easier to adapt actions once they move to a profile system (See my issue in quarto-actions quarto-dev/quarto-actions#44 (comment))
Originally posted by @Rahuketu86 in #998 (comment)
The text was updated successfully, but these errors were encountered: