Convert to gpm-style service #11

2021-03-11T14:56:11Z

jolheiser commented

2021-03-11 14:56:11 +00:00

(Migrated from gitea.com)

This is a massively breaking change from v0.3.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.3.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 (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.

There's also an SDK, which is nice to have.

This is a **massively** breaking change from `v0.3.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.3.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>

jolheiser commented

2021-04-23 03:21:48 +00:00

(Migrated from gitea.com)

Created a service branch for the older auto-updating system.

Created a `service` branch for the older auto-updating system.

Sign in to join this conversation.

No reviewers