Website Deployment

[sekwah41]

@roldanjr what are you currently using to deploy the gh-pages branch or are you manually committing it atm?

I can also sort that out to be automated too if you'd like.

[roldanjr]

I can also sort that out to be automated too if you'd like.

Currently, I manually deploy it to gh-pages using my computer.
I cannot deploy it manually right now due to some errors on my machine.

Yeah, I think it's better if there is some sort of automation for the deployment of the website.
I was planning to host it on Vercel and use NextJS instead of Gatsby when the time allows me to do it.

What do you think @sekwah41 .

[sekwah41]

Wait why would you host it on Vercel? Couldn't you just host it on Github pages with a custom dns if you are wanting that? Its what I do for my Minecraft plugin https://advancedportals.sekwah.com/docs/commands

Or is Vercel a framework? I've not used either of those directly before but I've heard of Gatsby.

[roldanjr]

The framework I used to built this website is GatsbyJS. But I find it very dependent on third-party plugins. Though it has some advantages also.

Most of the websites I built nowadays are built using NextJS framework and I hosted it on Vercel.
Every time there are some changes I made, Vercel kinda deploys it right away.

I will still think of it if it's worth the effort to do so.

But yeah, If you can automate the deployment of the current website it's better than revamping and transitioning to a different hosting provider.

Thank you in advance @sekwah41 🙇🏼‍♂️

[gillisandrew]

Having run into random errors in old gatsby projects, it's almost certainly an issue created by updating nodejs on your machine. Try running it with an older node (docker or through nvm). That said we can use github actions to automate the build and deploy the site without adopting nextjs.

[gillisandrew]

Didn't take too long to bring the webpage down 😆

Let me know if you need a hand getting that github action working haha

[sekwah41]

Ahh im looking now and reason it worked with manual deployments ie because the predeploy command has already got that variable set.

[sekwah41]

There are other issues with the workflow but I think that should be enough to get the site up again.

I've already pushed a revert commit though I'll do some more checks locally to see that its building with the right links.

[sekwah41]

Ah wait the issue is that the website is built against / as the root rather than pomatez/ usually I end up having this all configured in the config files. Usually in the libraries I use its just solely set in a config value.

[gillisandrew]

Its set in the config values here

Having had a closer look, a bunch of environment variables have to be set so maybe just hold off on deploy until we can get it properly configured.

[sekwah41]

Seems gatsby ignores it without the --prefix-paths which is what I meant.

What other env variables are needing to be set for now? At least locally to get back to the same state as the the currently deployed website it can be done using PREFIX_PATHS=true