search

logseq / publish-spa

A github action and CLI to publish logseq graphs as a SPA app
MIT License
244 stars 14 forks source link

Shared pages #14

Closed LoveSkylark closed 1 year ago

LoveSkylark commented 1 year ago

I've created a version of the 'Action' that allows you go keep your graph in a private repository and publish them as subfolder on their public .github.io site

This is for people that wish to have multiple Graphs and are only publishing parts of their content.

logseq-cldwalker commented 1 year ago

@LoveSkylark Hi. Thanks for trying to contribute. Unfortunately this contribution doesn't work for this repository as html generation is handled by logseq libraries and needs to stay in sync with the app's html. I do think your workflow is useful to document and I'd recommend creating your own repository for it. Once that is available, I'm happy to link to it in https://github.com/logseq/publish-spa#additional-links

LoveSkylark commented 1 year ago

Not sure I understand, your running a process that produces an output, that output gets placed into a separate branch "gh-pages". I'm still running the process locally inside the repo just pushing it out to my public repo when its finished. how does it matter if that output is place somewhere else?

Heres the proccess: I have a test log graphs on my LogSeq client, every time I update them they get pushed int my private individual repos for them. On that push the action to create html site gets triggered and it creates the web content but instead dropping the result into to the a "gh-pages" branch in the same reop it pushes them out to a publicly my publicly available repo https://loveskylark.github.io/ where it gets dropped into a subfolder (so I can have more than one LogSeq graph)

you can see the end result here: https://loveskylark.github.io/

This is how you set up the site github site: https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site

logseq-cldwalker commented 1 year ago

Put another way, this is a cool workflow but it's not something we're interested in maintaining. Happy to link to it if you make a repository for it

On Fri, 8 Sept 2023 at 06:10, Skylark @.***> wrote:

Not sure I understand, your running a process that produces an output, that output gets placed into a separate branch "gh-pages". I'm still running the process locally inside the repo just pushing it out to my public repo when its finished. how does it matter if that output is place somewhere else?

Heres the proccess: I have a test log graphs on my LogSeq client, every time I update them they get pushed int my private individual repos for them. On that push the action to create html site gets triggered and it creates the web content but instead dropping the result into to the a "gh-pages" branch in the same reop it pushes them out to a publicly my publicly available repo https://loveskylark.github.io/ where it gets dropped into a subfolder (so I can have more than one LogSeq graph)

you can see the end result here: https://loveskylark.github.io/

— Reply to this email directly, view it on GitHub https://github.com/logseq/publish-spa/pull/14#issuecomment-1711419532, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFVC5YAQ5N35PGO2IJMVTTXZLVI7ANCNFSM6AAAAAA4PGSYTU . You are receiving this because you modified the open/close state.Message ID: @.***>