Feature request: Proper support for GitHub Codespaces / dev containers about zola HOT 10 OPEN

I would find this useful, happy to help @InDieTasten

from zola.

I've drafted up a rough plan for how to achieve codespaces support in the description of this issue. @Keats Let me know, if you see any issues with that approach in regards to the rest of the system. I'm honestly not sure about the live reload websocket handling, so that part is more of an experiment than anything else ^^

@darrenmeehan I'll create a fork, add you as contributor and create some sub-issues within the fork. We can discuss within the fork, how we work together most effectively :)

I will also link the fork in here, once I've created it.

from zola.

I didn't even know about GitHub Codespaces until now so it would have to all come from PRs.

from zola.

@Keats I could definitely take a stab at this. Feel free to assign this to me, if you want me to explore this further and possibly create a PR for adding support.

from zola.

The fork for implementing this is located here: https://github.com/InDieTasten/zola-codespaces

The issue for more detailed tracking is located here: InDieTasten#1

from zola.

I also ran into this - in my case I'm not using GitHub Codespaces but a self-hosted VS Code with the Remote Tunnels feature where Microsoft provides a central domain to securly access my VS Code instance from anywhere.

At the moment I'm not able to access the zola serve process because it returns a Encountered an error: WebSocket Protocol Error: Unable to parse WebSocket key error that I don't have with other SSGs like Hugo or Jekyll.

from zola.

Just so people can dev for zola quickly, it might be quicker to implement a -disable-livereload flag for serve. Could that be an idea so that livereload.js doesn't block other assets from loading in the meantime?

from zola.

@nicodoggie I don't think implementing a new option for that is a good idea. It would change the interface for a temporary workaround. Also, the serve endpoint needs to be updated anyways due to

• #2465

It's just that I've been too busy the last couple weeks to dive into this again. However, if there is anyone interested in helping, that would be greatly appreciated.

from zola.

@InDieTasten any update on that?

from zola.

@Keats I'm currently very busy. I can push my WIP tonight. It's got the package updates in the cargo.toml figured out, but not yet modified the serve functionality to work with the new hyper types from v1

from zola.