alright, apparently, i got it up and running
how i did it:
I had my GitHub repo working for my notes,
I had a repo for my website up already
So I needed to make it so:
Whenever i updated my notes, my website repo would update, adding the new/updated blog posts, then rebuild the website, then upload it, all through github Actions.
- I had a Github repo working for my Obsidian notes
- I synced the repo with all my workspaces, through the ObsidianGit plugin
- I set the plugin to commit+sync the repo every minute in every workspace
- I had a repo setup for my website, so it could be updated from anywhere (or better yet, nowhere, through GitHub actions - more on that later)
- Link the BlogRepo to the WebsiteRepo, so the files on the BR (BlogRepo) would automatically become entries in my website when building it.
- Automate the building of the Website with npm run build through Github Actions.
- Automate the deployment of the Website with FTP through Github Actions.
I had no clue how i would do that, but the problem wasn't the obvious one: the website isnt code that i can just edit; in Next.Js you have to build the website into static before it is an actual file you can upload to an online file management system to become a website. I can do that pretty easily with the GH Actions, using npm run build when either my website or blog repos are commited to, etc. The actual problem was: How do I use cPanel to make these automated updates via FTP?
cPanel, for those who don't know, is a tool used as storage and storage management for webapps, and the interface is absolutely ancient. So after a few headslams against various different walls, I ultimately figured out how to connect my github actions to a secondary account i made on cPanel, where I could edit my files to my website through.
The only thing left was a few kinks with how these different accounts connect to cPanel, and where the uploaded files "land" on there, but after I figured that out there was only one thing left: Deciding what tool i would use for uploading via FTP.
I ended up going with SamKirkland/FTP-Deploy-Action, as it seemed a pretty popular one, with great support. so i tried it and..... well... i don't know.
I guess if you're reading this it means it worked!
I will also be adding an image to my post to see if it shows up on the website okay bye!
