Gitea &#39;pages&#39; #92

@tboerger commented on GitHub (Nov 29, 2016):

There have been already discussions about that in the past. This is a pretty huge feature and it requires additional domain/subdomain handling.

@tboerger commented on GitHub (Nov 29, 2016): There have been already discussions about that in the past. This is a pretty huge feature and it requires additional domain/subdomain handling.

GiteaMirror commented

@auuuuuzzzzzpallauzzzzz commented on GitHub (Nov 29, 2016):

Why not instead just

let users have a repository called "project_name.pages.git"
let the website admin define a single suburl like "pages.hostname.com"
when Gitea detects the URL "pages.hostname.com/username/project" it automatically reads the HTML from "project_name.pages.git"

Maybe the URL is too long? Or are there security problems?

@auuuuuzzzzzpallauzzzzz commented on GitHub (Nov 29, 2016): Why not instead just - let users have a repository called "project_name.pages.git" - let the website admin define a single suburl like "pages.hostname.com" - when Gitea detects the URL "pages.hostname.com/username/project" it automatically reads the HTML from "project_name.pages.git" Maybe the URL is too long? Or are there security problems?

GiteaMirror commented

@tboerger commented on GitHub (Nov 29, 2016):

It must be a different domain because of security, otherwise somebody can inject malicious code that steals the session cookie.

@tboerger commented on GitHub (Nov 29, 2016): It must be a different domain because of security, otherwise somebody can inject malicious code that steals the session cookie.

GiteaMirror commented

@bkcsoft commented on GitHub (Nov 29, 2016):

this should be done with CI and a http-proxy (like nginx, træfik, etc)

@bkcsoft commented on GitHub (Nov 29, 2016): this should be done with CI and a http-proxy (like nginx, træfik, etc)

GiteaMirror commented

@tboerger commented on GitHub (Nov 29, 2016):

Some static page feature should be nice, but first it requires a proper proposal so that somebody can estimate the requirements.

@tboerger commented on GitHub (Nov 29, 2016): Some static page feature should be nice, but first it requires a proper proposal so that somebody can estimate the requirements.

GiteaMirror commented

@bkcsoft commented on GitHub (Dec 2, 2016):

Even static page required the use of a different domain (because JS...). ALL other git services implement this by using a CI & http-proxy...

@bkcsoft commented on GitHub (Dec 2, 2016): Even static page required the use of a different domain (because JS...). ALL other git services implement this by using a CI & http-proxy...

GiteaMirror commented

@tboerger commented on GitHub (Dec 2, 2016):

It must be a different domain because of security, otherwise somebody can inject malicious code that steals the session cookie.

But basic functionality to provide that can also be integrated into Gitea. Maybe at some point if we support plugins.

@tboerger commented on GitHub (Dec 2, 2016): > It must be a different domain because of security, otherwise somebody can inject malicious code that steals the session cookie. But basic functionality to provide that can also be integrated into Gitea. Maybe at some point if we support plugins.

GiteaMirror commented

@bkcsoft commented on GitHub (Dec 2, 2016):

Well yes, we could build it... but unless we add multi-host we're screwed 😛

@bkcsoft commented on GitHub (Dec 2, 2016): Well yes, we could _build_ it... but unless we add multi-host we're screwed 😛

GiteaMirror commented

@tboerger commented on GitHub (Dec 2, 2016):

And to clarify all requirements and all the changes this needs i suggested a proposal ;)

@tboerger commented on GitHub (Dec 2, 2016): And to clarify all requirements and all the changes this needs i suggested a proposal ;)

GiteaMirror commented

@lunny commented on GitHub (Feb 23, 2017):

In fact, we can start a new web service for the page on the same binary according to user's config.

@lunny commented on GitHub (Feb 23, 2017): In fact, we can start a new web service for the page on the same binary according to user's config.

GiteaMirror commented

@ShalokShalom commented on GitHub (Jul 27, 2017):

It's very easy to implement this with Caddy: https://caddyserver.com/docs/http.git

@ShalokShalom commented on GitHub (Jul 27, 2017): It's very easy to implement this with Caddy: https://caddyserver.com/docs/http.git

GiteaMirror commented

@techknowlogick commented on GitHub (Jan 23, 2019):

Closing this as it can be better served by something such as Drone, Minio & Caddy together (or as @ShalokShalom mentioned, just caddy in itself).

@techknowlogick commented on GitHub (Jan 23, 2019): Closing this as it can be better served by something such as Drone, Minio & Caddy together (or as @ShalokShalom mentioned, just caddy in itself).

GiteaMirror commented

@ghost commented on GitHub (Jan 29, 2019):

A pages feature is the only reason I would use GitLab CE over Gitea.

@ghost commented on GitHub (Jan 29, 2019): A pages feature is the only reason I would use GitLab CE over Gitea.

GiteaMirror commented

@davidak commented on GitHub (Jan 30, 2019):

@archiebaer when you not want to setup your own server, have you considered hosting your static website at https://neocities.org/?

@davidak commented on GitHub (Jan 30, 2019): @archiebaer when you not want to setup your own server, have you considered hosting your static website at https://neocities.org/?

GiteaMirror commented

@pat-s commented on GitHub (Feb 13, 2019):

@ShalokShalom Is there any detailed guide on how to use caddy specifically with Gitea? Trying since hours to get this running :/

@pat-s commented on GitHub (Feb 13, 2019): @ShalokShalom Is there any detailed guide on how to use `caddy` specifically with Gitea? Trying since hours to get this running :/

GiteaMirror commented

@ShalokShalom commented on GitHub (Feb 20, 2019):

@pat-s Sorry for the delay. Did you get it running?

@ShalokShalom commented on GitHub (Feb 20, 2019): @pat-s Sorry for the delay. Did you get it running?

GiteaMirror commented

@pat-s commented on GitHub (Feb 20, 2019):

No, not yet. A guide would be highly appreciated.

@pat-s commented on GitHub (Feb 20, 2019): No, not yet. A guide would be highly appreciated.

GiteaMirror commented

@bricewge commented on GitHub (Feb 23, 2019):

@pat-s Here is a working example where a hugo blog is build on the caddy server; note that you will need a caddy binary compiled with the git plugin.

@bricewge commented on GitHub (Feb 23, 2019): @pat-s [Here](https://gist.github.com/bricewge/ca40d415f5f3a45de9c04e779ac68e03) is a working example where a hugo blog is build on the caddy server; note that you will need a caddy binary compiled with the git plugin.

GiteaMirror commented

@ShalokShalom commented on GitHub (Mar 1, 2019):

Can we put this into the documentation?

@ShalokShalom commented on GitHub (Mar 1, 2019): Can we put this into the documentation?

GiteaMirror commented

@pat-s commented on GitHub (Mar 1, 2019):

Hm, I got my site working locally now. However, I cannot wrap my head around how I should serve/push it to the Gitea domain.

domain {
  root ./my-site
	git {
		repo        <git repo>
		path        .repo
		interval    3600
		then        R -q -e "bookdown::render_book('.', output_dir = '../')"
	}
}

I always get the following error:

acme: Obtaining bundled SAN certificate
2019/03/01 23:51:02 [INFO] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/K_LkKK7jteSA8vJzWcpIcP4HEzmrsK-aKLfEvUNENYg
2019/03/01 23:51:02 [INFO] acme: use tls-alpn-01 solver
2019/03/01 23:51:02 [INFO] acme: Trying to solve TLS-ALPN-01
2019/03/01 23:51:08 [geoinf.uni-jena.de] failed to obtain certificate: acme: Error -> One or more domains had a problem:

Also this video did not help.

How can I deploy the site to, let's say, <domain>/<repo>/<caddy> (https://123.org/repo/caddy)?

@pat-s commented on GitHub (Mar 1, 2019): Hm, I got my site working locally now. However, I cannot wrap my head around how I should serve/push it to the Gitea domain. ```sh domain { root ./my-site git { repo <git repo> path .repo interval 3600 then R -q -e "bookdown::render_book('.', output_dir = '../')" } } ``` I always get the following error: ``` acme: Obtaining bundled SAN certificate 2019/03/01 23:51:02 [INFO] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/K_LkKK7jteSA8vJzWcpIcP4HEzmrsK-aKLfEvUNENYg 2019/03/01 23:51:02 [INFO] acme: use tls-alpn-01 solver 2019/03/01 23:51:02 [INFO] acme: Trying to solve TLS-ALPN-01 2019/03/01 23:51:08 [geoinf.uni-jena.de] failed to obtain certificate: acme: Error -> One or more domains had a problem: ``` Also [this video](https://www.youtube.com/watch?v=dmat1MUT0fc) did not help. How can I deploy the site to, let's say, `<domain>/<repo>/<caddy>` (https://123.org/repo/caddy)?

GiteaMirror commented

@bricewge commented on GitHub (Mar 2, 2019):

@ShalokShalom You should write a PR to add it to the docs then.

@pat-s It doesn't look like a good idea to serve your website under the same domain as gitea https://github.com/go-gitea/gitea/issues/6163#issuecomment-466601351; Github and Gitlab are using subdomains to publish pages. Your error message is related to caddy automatic HTTPS but I don't think it's the right place to try to solve it, you can ask about it in the caddy's forum.

@bricewge commented on GitHub (Mar 2, 2019): @ShalokShalom You should write a PR to add it to the docs then. @pat-s It doesn't look like a good idea to serve your website under the same domain as gitea https://github.com/go-gitea/gitea/issues/6163#issuecomment-466601351; Github and Gitlab are using subdomains to publish pages. Your error message is related to caddy automatic HTTPS but I don't think it's the right place to try to solve it, you can ask about it in the caddy's [forum](https://caddy.community/).

GiteaMirror commented

@ShalokShalom commented on GitHub (Mar 7, 2019):

And post the solution here then, so others who find this post can relate. I can create an article for the docs then, have it not done by myself yet.

@ShalokShalom commented on GitHub (Mar 7, 2019): And post the solution here then, so others who find this post can relate. I can create an article for the docs then, have it not done by myself yet.

GiteaMirror commented

@hoijui commented on GitHub (May 1, 2019):

Let's say I have everything setup: a caddy server with git support, ready to serve repos under a sub-domain.
How would I make it, so that if a gitea user creates a new repository, and uploads a g-pages branch, for example, it will be hosted on repo.user.sub-domain.domain? Or more specifically: how woudl I start a script that triggers the creation of a new sub-domain and directory on the cady server, clones the repo and sets up a hook so changes to the g-pages branch get published immediately?
So the question is mostly, about how to automate the process; how to trigger a web-repo-creating script from within gitea, when a new repo is created.

@hoijui commented on GitHub (May 1, 2019): Let's say I have everything setup: a caddy server with git support, ready to serve repos under a sub-domain. How would I make it, so that if a gitea user creates a new repository, and uploads a `g-pages` branch, for example, it will be hosted on repo.user.sub-domain.domain? Or more specifically: how woudl I start a script that triggers the creation of a new sub-domain and directory on the cady server, clones the repo and sets up a hook so changes to the `g-pages` branch get published immediately? So the question is mostly, about how to automate the process; how to trigger a web-repo-creating script from within gitea, when a new repo is created.

GiteaMirror commented

@hoijui commented on GitHub (May 1, 2019):

btw, we plan to set this up while documenting it. if we manage to do so, the documentation wil be published (and lined to here)

@hoijui commented on GitHub (May 1, 2019): btw, we plan to set this up while documenting it. if we manage to do so, the documentation wil be published (and lined to here)

GiteaMirror commented

@bricewge commented on GitHub (May 1, 2019):

I don't think gitea can do that yet but it would be great to have this feature. A hacky workaround would be to use inotifywait or systemd's .path to monitor the creation of the directories $GITEA_WORK_DIR/repositories/*/g-pages.

@bricewge commented on GitHub (May 1, 2019): I don't think `gitea` can do that yet but it would be great to have this feature. A *hacky* workaround would be to use `inotifywait` or systemd's `.path` to monitor the creation of the directories `$GITEA_WORK_DIR/repositories/*/g-pages`.

GiteaMirror commented

@hoijui commented on GitHub (May 1, 2019):

oh wow... thanks for the info.

so basically I would do this:

monitor $GITEA_WORK_DIR/repositories/*/* for the creation of new repos
for each new repo, install an update git hook (see end of page)
in this hook script, I would thenn call an other script, triggering the creation/update of a subdomain and web-server directory for this repo, if the g-pages branch is updated, if such repo does not yet exist

@hoijui commented on GitHub (May 1, 2019): oh wow... thanks for the info. so basically I would do this: * monitor `$GITEA_WORK_DIR/repositories/*/*` for the creation of new repos * for each new repo, install an `update` [git hook (see end of page)](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) * in this hook script, I would thenn call an other script, triggering the creation/update of a subdomain and web-server directory for this repo, if the `g-pages` branch is updated, if such repo does not yet exist

GiteaMirror commented

@hoijui commented on GitHub (May 1, 2019):

links for documentation:

Caddy - static web server software (sources, APL 2.0)
Drone - CI/build-server/Continuous Delivery platform (sources, APL 2.0)
MinIO - object storage for AI (sources, APL 2.0) - Why would we want to use this/what for?

@hoijui commented on GitHub (May 1, 2019): links for documentation: * [Caddy](https://caddyserver.com/docs/http.git) - static web server software ([sources](https://github.com/mholt/caddy), APL 2.0) * [Drone](https://drone.io/) - CI/build-server/Continuous Delivery platform ([sources](https://github.com/drone/drone), APL 2.0) * [MinIO](https://min.io/) - object storage for AI ([sources](https://github.com/minio/minio), APL 2.0) - _Why would we want to use this/what for?_

GiteaMirror commented

@ShalokShalom commented on GitHub (May 1, 2019):

You could host it via IPFS: This means no Server are in place, all decentralised

@ShalokShalom commented on GitHub (May 1, 2019): You could host it via IPFS: This means no Server are in place, all decentralised

GiteaMirror commented