While I was writing support for .patch, I've stumbled upon go-git not having support for patches.

I opened an issue, to either add better support for patches or writing format-patch on go-git. We still can write that manually on smithy, but I would rather wait, what do you think?

• fix closing tag in tree template
• remove redundant repo name in commit template
• always call repository name RepoName
• use consistent base template context
• pass context to the header template
• add dependency for binary on include files

commit e4b24bd9b86f91e590ca0df270d249039a3503b2 this means golang is not the only dependence, so we need to use also statik from comamnd system to able to produce distribution packages from this great tool!

Hi,

when I run the make command I get the following error

[email protected]:~/Development/GolangDev/smithy$ make

mkdir -p bin

go mod download

go build -o bin/statik /src/github.com/rakyll/statik/statik.go

stat /src/github.com/rakyll/statik/statik.go: directory not found

make: *** [Makefile:12: bin/statik] Error 1

This new view introduces a text/plain version of a single patch. It has some differences when using git format-patch and will match more the --no-stats version of the refered git command. This is due the fact that go-git has no support for summary for diffs yet (I have a patch waiting for over a month there) 1.

There's also a problem when dealing with the root commit, which go-git Patch API still doesn't support 2.

Files immediately under the root of the repo were being rendered as ././name because the template includes a static ./ value. Remove that so the path is always accurate.

You say that the only dependency is Golang in the README. But when I try to compile the project by doing

$ git clone https://github.com/honza/smithy
$ make 

I get

make: statik: No such file or directory
make: *** [all] Error 

Maybe the documentation should be updated ?

When using the files directly from include Smithy can't start, because header.html tries to call {{css}} which seems to be not defined, although I can see it here. My knowledge of Go is limited though.

Wrap the ref in paragraph tags so the vertical alignment is consistent with the content in the blob.html template, so that when the user clicks through from a directory listing to an individual file the header section of the page does not appear to change sizes.

Remove the extra path value, since it is the same as the parent path.

The default configuration generated by smithy generate did not include the static.prefix value, which is needed to make the templates render. This commit adds a default value based on the setting in the README.

Hi, what would a basic service file fo smithy look like?

For example, with runit could it just be to start the server on boot?

#!/bin/sh

exec smithy serve --config config.yml 2>&1

I guess the service would also need to restart when a git repository is pushed to or should that be handled by a git hook instead?

What would be the ideal set up?

A cool feature would be support downloading tarballs from refs, specially for tags and commits.

This probably would involve firing up git-archive (1) if go-git doesn't have support for this already.

Today we have a bug where if a repository is under a directory, we don't load it correctly. As I wrote a patch to fix this, I started to wonder if adding support for grouping repositories would not make more sense. I think this should be discussed if we should infer if the repository path has a slash, we should group it (cgit does this), or if we should add first class support to the project group, with its title, description, etc. It would also make more sense considering that smithy shows "Projects", and some are often made up of several different repositories.