Skip to content

host static html and/or markdown pages #3834

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
laoshaw opened this issue Apr 23, 2018 · 10 comments
Closed

host static html and/or markdown pages #3834

laoshaw opened this issue Apr 23, 2018 · 10 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@laoshaw
Copy link

laoshaw commented Apr 23, 2018

other than the wiki, is it possible to host static html and/or markdown pages in gitea? similar to what github does, if possible, make those page only accessible after login as what wiki does, is this possible?

this way I can host documentations along with source code in gitea and be able to view the doc via web.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Apr 23, 2018
@lunny
Copy link
Member

lunny commented Apr 23, 2018

I think we could listen another port which defaultly don't open to host the generated web site.

@pedro-ricardo
Copy link

Is there a way to vote for this? I'ts been quite a while since this feature was requested . . .
We use Gitea in our company and the software documentation is automatically generated in html. Those files are committed and kept in the repo.
If there was a way to access (serve) those html files as easy as accessing the Wiki page ... It would be awesome.

In my opinion it makes "keeping the documentation up to date" a much easier job.

@koalp
Copy link
Contributor

koalp commented Sep 6, 2021

@pedro-ricardo I think that you can add a “thumb up” reaction to the comment of the issue.

I previously upvoted this feature but now think that it isn't in the scope of gitea and should rather be a different software, that way it could be used with other software forges. (however, no such software exist yet to my knowledge).

@pedro-ricardo
Copy link

I see, thanks I'll do it ...
I think this issue and the duplicates that show up from time to time are a request to implement something like GitHub offers and people liked it.

In my opinion it is a way to keep stuff like software documentations in the repository, instead of the separated Wiki markdown pages. And by doing that it increases the maintainability of this documentation.

@6543
Copy link
Member

6543 commented Sep 6, 2021

In my opinion its also not in scope of gitea ...

And there exist software: https://codeberg.org/momar/codeberg-pages

@6543
Copy link
Member

6543 commented Sep 6, 2021

A nice "hack" you cold also do: use external renderer 'cat' to show html files rendered like you have with markdown ;)

https://docs.gitea.io/en-us/external-renderers/

@laoshaw
Copy link
Author

laoshaw commented Sep 6, 2021

considering github is using pages separately from the code repository, displaying html from the same repository is probably technically 'impossible' for gitea too, it has to have its own (http) port.

but github/gitea can render markdown right inside the repository pretty well, similar to those syntax highlighted source code files, it's just hard to navigate(e.g. built-in octotree),gitea has similar problem. as far as documentation goes, making all document as markdown files might be the easy way out(instead of html)

markdown in gitea can show images directly, however it can not directly support video playing(be it a local video file or a video link to, say, youtube), you have to click on it and play them in a separate gitea window, which is a pity, otherwise I'm fine with markdown for all my documentations.

@pedro-ricardo
Copy link

Hold on @laoshaw ... This whole operation was your idea ... 😆

We use html because it is automatically generated, looks pretty and it is easy to navigate ...
About being easier in comparison of with Markdown, I was just talking about the Wiki pages that are stored in a separated place.

And in the end ... Well, I'd like it ... But if it is out of the software scope, let's just move on. 👍

@6543
Copy link
Member

6543 commented Dec 6, 2021

UPDATE: the project (now at https://codeberg.org/Codeberg/pages-server) is now live and I'm currently refactoring stuff to make it usable to all gitea instances who want that feature

can we close this issue?

@laoshaw
Copy link
Author

laoshaw commented Dec 6, 2021

Yes Thanks.

@laoshaw laoshaw closed this as completed Dec 6, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

5 participants