No description or website provided.
Scala HTML
Clone or download
Latest commit 5fce5df Jun 29, 2018
Permalink
Failed to load latest commit information.
project Bump to 1.7.1 Jun 5, 2018
src/main Bump to 1.7.1 Jun 10, 2018
.gitignore initial commit Dec 21, 2015
.scalafmt.conf use scalafmt as the code formatter, add sbt-updates Apr 24, 2018
.travis.yml Update travis build script Jun 29, 2018
LICENSE add license Dec 22, 2015
README.md Update README.md Jun 29, 2018
build.sbt Bump to 1.7.1 Jun 5, 2018

README.md

Gitbucket-Pages-Plugin Gitter Travis

This plugin provides Project Pages functionality for GitBucket based repositories.

User guide

This plugin serves static files directly from one of the following places:

  • gb-pages branch (with fallback to gh-pages to be compatible with github, this is the default)
  • master branch
  • docs folder under master branch

Quick start

  • create a directory or branch if necessary (eg. create an orphan branch called gb-pages: git checkout --orphan gb-pages && git rm -f $(git ls-files))
  • create a static site under this branch. E.g. echo '<h1>hello, world</h1>' > index.html to create a simple file.
  • commit && push to gitbucket this orphan branch
  • open the browser and point to <your repo url>/pages

Note: This plugin won't render markdown content. To render markdown content, use the GitBucket Wiki functionality, or use one of the many static site generators (e.g. jekyll, hugo)

Installation

This plugin is bundled with newer version of GitBucket, for older version please follow the instruction below

Install manually

  • download from plugin registry
  • copy the jar file to <GITBUCKET_HOME>/plugins/ (GITBUCKET_HOME defaults to ~/.gitbucket)
  • enable it in plugin settings (you may need to restart gitbucket)

Versions

pages version gitbucket version
1.7.0 4.23.0
1.6.0 4.19.0
1.5.0 4.15.0
1.3 4.14.1
1.2 4.13
1.1 4.11
1.0 4.10
0.9 4.9
0.8 4.6
0.7 4.3 ~ 4.6
0.6 4.2.x
0.5 4.0, 4.1
0.4 3.13
0.3 3.12
0.2 3.11
0.1 3.9, 3.10

Security (panic mode)

To prevent XSS, one must use two different domains to host the pages and Gitbucket itself. Below is a working example of nginx configuration to achieve that.

server {
    listen 80;
    server_name git.local;

    location ~ ^/([^/]+)/([^/]+)/pages/(.*)$ {
        rewrite  ^/([^/]+)/([^/]+)/pages/(.*)$  http://doc.local/$1/$2/pages/$3  redirect;
    }

    location / {
        proxy_pass http://127.0.0.1:8080;
    }
}

server {
    listen 80;
    server_name doc.local;

    location ~ ^/([^/]+)/([^/]+)/pages/(.*)$ {
        proxy_pass http://127.0.0.1:8080;
    }

    location / {
        return 403;
    }
}

CI