jolheiser
/
vanity
1
0
Fork 0
Code Issues Pull Requests Releases 5 Activity
vanity/go.mod

20 lines
609 B
Modula-2
Raw Normal View History

Initial commit Signed-off-by: jolheiser <john.olheiser@gmail.com>
2020-02-21 04:39:03 +00:00
module go.jolheiser.com/vanity
Shiny things (#8) Resolves #4 Resolves #5 Resolves #6 Change list: * Adds topics format * Groups projects by their topics/tags, any without topics are tossed in `other` * Adds minimal page for `go-get` or `git-import` URL query parameters * Changes the version information to explicitly mention Vanity and Go. * Adds manual update mode as an alternative to the automatic intervals. * Moved templates to `.tmpl` files and using `//go:embed` to add to binary. Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/8 Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-committed-by: John Olheiser <john.olheiser@gmail.com>
2021-02-21 20:23:06 +00:00
go 1.16
Initial commit Signed-off-by: jolheiser <john.olheiser@gmail.com>
2020-02-21 04:39:03 +00:00
Convert to gpm-style service (#11) This is a **massively** breaking change from `v0.2.0`. For consumers there will be no difference, `go-get` and `git-import` are both still supported. The change will be for the admin regarding how package management works. Prior to merging, `v0.2.0` should be moved to another branch in case myself or another party wants to continue with that style of service. This version follows a similar implementation to [gpm](https://gitea.com/jolheiser/gpm) (and indeed, some code was copied nearly line-by-line) ----- Vanity runs as a service, same as before. However, rather than automatic cron-style updates using a third-party API, now the service owner uses their local `vanity` binary with a matching `token` to... * `vanity add` a new package * `vanity update` an existing package * `vanity remove` a package This allows much finer control over which packages are in the service and should required almost no downtime once the service is started other than to update the service itself. As well, it allows mixing of git providers. <small>There's also an SDK, which is nice to have.</small> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/11 Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-committed-by: John Olheiser <john.olheiser@gmail.com>
2021-04-23 03:21:53 +00:00
replace go.jolheiser.com/vanity/go-vanity => ./go-vanity
Initial commit Signed-off-by: jolheiser <john.olheiser@gmail.com>
2020-02-21 04:39:03 +00:00
require (
Convert to gpm-style service (#11) This is a **massively** breaking change from `v0.2.0`. For consumers there will be no difference, `go-get` and `git-import` are both still supported. The change will be for the admin regarding how package management works. Prior to merging, `v0.2.0` should be moved to another branch in case myself or another party wants to continue with that style of service. This version follows a similar implementation to [gpm](https://gitea.com/jolheiser/gpm) (and indeed, some code was copied nearly line-by-line) ----- Vanity runs as a service, same as before. However, rather than automatic cron-style updates using a third-party API, now the service owner uses their local `vanity` binary with a matching `token` to... * `vanity add` a new package * `vanity update` an existing package * `vanity remove` a package This allows much finer control over which packages are in the service and should required almost no downtime once the service is started other than to update the service itself. As well, it allows mixing of git providers. <small>There's also an SDK, which is nice to have.</small> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/11 Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-committed-by: John Olheiser <john.olheiser@gmail.com>
2021-04-23 03:21:53 +00:00
github.com/AlecAivazis/survey/v2 v2.2.8
Vanity overhaul (#3) More debug output and template fixes Signed-off-by: jolheiser <john.olheiser@gmail.com> README cleanup Signed-off-by: jolheiser <john.olheiser@gmail.com> Better config options, change package structure Signed-off-by: jolheiser <john.olheiser@gmail.com> Add GitLab support Signed-off-by: jolheiser <john.olheiser@gmail.com> Initial Overhaul Signed-off-by: jolheiser <john.olheiser@gmail.com> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/3
2020-09-12 15:23:25 +00:00
github.com/cpuguy83/go-md2man/v2 v2.0.0 // indirect
github.com/go-chi/chi v4.1.2+incompatible
github.com/urfave/cli/v2 v2.2.0
Convert to gpm-style service (#11) This is a **massively** breaking change from `v0.2.0`. For consumers there will be no difference, `go-get` and `git-import` are both still supported. The change will be for the admin regarding how package management works. Prior to merging, `v0.2.0` should be moved to another branch in case myself or another party wants to continue with that style of service. This version follows a similar implementation to [gpm](https://gitea.com/jolheiser/gpm) (and indeed, some code was copied nearly line-by-line) ----- Vanity runs as a service, same as before. However, rather than automatic cron-style updates using a third-party API, now the service owner uses their local `vanity` binary with a matching `token` to... * `vanity add` a new package * `vanity update` an existing package * `vanity remove` a package This allows much finer control over which packages are in the service and should required almost no downtime once the service is started other than to update the service itself. As well, it allows mixing of git providers. <small>There's also an SDK, which is nice to have.</small> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/11 Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-committed-by: John Olheiser <john.olheiser@gmail.com>
2021-04-23 03:21:53 +00:00
go.etcd.io/bbolt v1.3.5
Vanity overhaul (#3) More debug output and template fixes Signed-off-by: jolheiser <john.olheiser@gmail.com> README cleanup Signed-off-by: jolheiser <john.olheiser@gmail.com> Better config options, change package structure Signed-off-by: jolheiser <john.olheiser@gmail.com> Add GitLab support Signed-off-by: jolheiser <john.olheiser@gmail.com> Initial Overhaul Signed-off-by: jolheiser <john.olheiser@gmail.com> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/3
2020-09-12 15:23:25 +00:00
go.jolheiser.com/beaver v1.0.2
Convert to gpm-style service (#11) This is a **massively** breaking change from `v0.2.0`. For consumers there will be no difference, `go-get` and `git-import` are both still supported. The change will be for the admin regarding how package management works. Prior to merging, `v0.2.0` should be moved to another branch in case myself or another party wants to continue with that style of service. This version follows a similar implementation to [gpm](https://gitea.com/jolheiser/gpm) (and indeed, some code was copied nearly line-by-line) ----- Vanity runs as a service, same as before. However, rather than automatic cron-style updates using a third-party API, now the service owner uses their local `vanity` binary with a matching `token` to... * `vanity add` a new package * `vanity update` an existing package * `vanity remove` a package This allows much finer control over which packages are in the service and should required almost no downtime once the service is started other than to update the service itself. As well, it allows mixing of git providers. <small>There's also an SDK, which is nice to have.</small> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/11 Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-committed-by: John Olheiser <john.olheiser@gmail.com>
2021-04-23 03:21:53 +00:00
go.jolheiser.com/overlay v0.0.2
go.jolheiser.com/vanity/go-vanity v0.0.0-00010101000000-000000000000
golang.org/x/net v0.0.0-20200822124328-c89045814202 // indirect
Vanity overhaul (#3) More debug output and template fixes Signed-off-by: jolheiser <john.olheiser@gmail.com> README cleanup Signed-off-by: jolheiser <john.olheiser@gmail.com> Better config options, change package structure Signed-off-by: jolheiser <john.olheiser@gmail.com> Add GitLab support Signed-off-by: jolheiser <john.olheiser@gmail.com> Initial Overhaul Signed-off-by: jolheiser <john.olheiser@gmail.com> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/3
2020-09-12 15:23:25 +00:00
golang.org/x/sys v0.0.0-20200909081042-eff7692f9009 // indirect
Convert to gpm-style service (#11) This is a **massively** breaking change from `v0.2.0`. For consumers there will be no difference, `go-get` and `git-import` are both still supported. The change will be for the admin regarding how package management works. Prior to merging, `v0.2.0` should be moved to another branch in case myself or another party wants to continue with that style of service. This version follows a similar implementation to [gpm](https://gitea.com/jolheiser/gpm) (and indeed, some code was copied nearly line-by-line) ----- Vanity runs as a service, same as before. However, rather than automatic cron-style updates using a third-party API, now the service owner uses their local `vanity` binary with a matching `token` to... * `vanity add` a new package * `vanity update` an existing package * `vanity remove` a package This allows much finer control over which packages are in the service and should required almost no downtime once the service is started other than to update the service itself. As well, it allows mixing of git providers. <small>There's also an SDK, which is nice to have.</small> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: https://gitea.com/jolheiser/vanity/pulls/11 Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-committed-by: John Olheiser <john.olheiser@gmail.com>
2021-04-23 03:21:53 +00:00
golang.org/x/text v0.3.3 // indirect
Initial commit Signed-off-by: jolheiser <john.olheiser@gmail.com>
2020-02-21 04:39:03 +00:00
)