🐛 Publishing my Obsidian vault discrepancies
Closed this issue · 7 comments
I followed this tutorial https://datahub.io/@olayway/docs/Publish%20your%20Obsidian%20vault and tried publishing my Obsidian vault but got a few issues, see below:
Issues discovered
- Is it not possible to publish just some directories and not my whole vault? I was under the impression that I was selecting only one particular folder/directory and all my vault got pushed to GitHub which was terrible because some notes are not supposed to be public
- I found out that I didn't have a readme and that's why I had a 404. I think the instructions in the tutorial are misleading because of the following sentence "2.7. Make sure the checkbox "Initialise this repository with a README" is unchecked". See https://datahub.io/@olayway/docs/Publish%20your%20Obsidian%20vault
- Different subfolders: The subfolders in my Obsidian vault are different from the ones published with Datahub Cloud (see screenshots below)
Different subfolders
See in my obsidian vault folder file as an example the Datahub Cloud directory:
This is what it looks like when published with Datahub Cloud:
And you see that I have pushed all changes and there aren't any pending changes on my Github Desktop (everything is synced):
@olayway assigning it to you cos I made this repo private (contains some sensitive info which I don't want to disclose to the whole world) and added you as a collaborator so only you have access to debug this for now. Please check and if you think someone else should handle it let me know so I give someone else access as well.
@Daniellappv It looks like you initialised your local repository in the whole Obsidian-Vault folder. That's why the whole vault got pushed to the remote repository. I don't think there is any other explanation for that. When creating that local repository, you need to make sure that the path you provide in the window below is pointing only to the subfolder you want to backup to github repository.
To fix this you can:
- Remove the remote repository
- Remove the local repository:
- Open GitHub Desktop
- Open your Obsidian-Vault repostory
- From window tabs at the top choose Repository -> Remove
- Recreate the repository making sure you select the path to the subfolder you want to publish
Let me know if that worked
I found out that I didn't have a readme and that's why I had a 404. I think the instructions in the tutorial are misleading because of the following sentence "2.7. Make sure the checkbox "Initialise this repository with a README" is unchecked". See https://datahub.io/@olayway/docs/Publish%20your%20Obsidian%20vault
Yes, I agree, this should be rephrased to sth like:
"2.7. If your Obsidian vault doesn't have a root README.md or index.md file yet, you can check the "Initialise this repository with a README" checkbox to have it created for you. It will serve as a landing page of your site.".
Different subfolders: The subfolders in my Obsidian vault are different from the ones published with Datahub Cloud (see screenshots below)
I think you mean file names. Yes, they are different. In the finder window on your Mac you can see file names. DataHub Cloud tries to display page titles instead. And if title is not provided, it tries to extract it. However now lookin at your example, I think it should only try to extract h1 level heading and only if no content is found before them. Currently it also extracts h2s which shouldn't happen.
hey @olayway all great, just one comment related to your last comment. These are the file names on my Mac:
And they are totally different from the ones published for some reason. Seems to be a 🐛
I'll close this one and open an issue for incorrectly extracted page titles / incorrect default values that should in your case be file names obviously.
See #1219