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
Is there a recommended workflow for having a vitePress project in a local directory, that can reference another folder location external to the project directory for the markdown content?
Reading through VitePress doco, I'm attempting to use;
Where instead of hosting my markdown data within .\docs, I'm attempting to use a shared folder from OneDrive, Google Drive, DropBox of a folder named 'cloud-docs' - for example;
Unfortunately, using the exact same mirrored md files within this cloud location, the pages fail to render during the docs:dev, and a build attempt returns many broken links that aren't otherwise there when (the same) markdown files are stored within the project docs directory.
I've tried creating a symbolic-link/junction to that same cloud directory to simulate those markdown files being local to the project, for example;
.\docs\cloud-docs\
srcDir: './cloud-docs/'
But still encountered the same/similar dev and build issues. The problem looks to be that vitepress simply won't view those cloud-doc markdown files relatively to the project.
In our user case, the authors are saving their markdown files into a cloud service, and I'm hoping to avoid copying that data from the cloud folders into the project folders - as would prefer on set of markdown docs to work with.
I've searched for similar posts but couldn't find any - so am not sure if this is a bug or a feature request. 😅
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey all,
Is there a recommended workflow for having a vitePress project in a local directory, that can reference another folder location external to the project directory for the markdown content?
Reading through VitePress doco, I'm attempting to use;
export default { srcDir: './src' }
https://vitepress.dev/reference/site-config#srcdir
Where instead of hosting my markdown data within .\docs, I'm attempting to use a shared folder from OneDrive, Google Drive, DropBox of a folder named 'cloud-docs' - for example;
srcDir: 'C:/Users/%USERPROFILE%/OneDrive/cloud-docs'
Unfortunately, using the exact same mirrored md files within this cloud location, the pages fail to render during the docs:dev, and a build attempt returns many broken links that aren't otherwise there when (the same) markdown files are stored within the project docs directory.
I've tried creating a symbolic-link/junction to that same cloud directory to simulate those markdown files being local to the project, for example;
.\docs\cloud-docs\
srcDir: './cloud-docs/'
But still encountered the same/similar dev and build issues. The problem looks to be that vitepress simply won't view those cloud-doc markdown files relatively to the project.
In our user case, the authors are saving their markdown files into a cloud service, and I'm hoping to avoid copying that data from the cloud folders into the project folders - as would prefer on set of markdown docs to work with.
I've searched for similar posts but couldn't find any - so am not sure if this is a bug or a feature request. 😅
Beta Was this translation helpful? Give feedback.
All reactions