Migrate away from weegie.kde.org
Closed, ResolvedPublic

Description

Services

  • packaging.neon (gitolite + cgit + ssh access to push + git://)
  • releases.neon (static file hosting of release metadata, hit at least once a day by clients, can't be signed and can't be redirected I think)

releases.neon

  • Only static files
  • Requires logging of HTTP requests (specifically their query parameters as they can contain a system-id identifying the installation)
  • Possibly requires a secondary service to process the logged requests, so e.g. a cron that throws the logged data at some other server
sitter created this task.Jun 9 2016, 9:02 AM
sitter renamed this task from Migrate away from weegie.kde.rog to Migrate away from weegie.kde.org.
sitter updated the task description. (Show Details)Aug 8 2016, 6:08 AM

releases.neon is used by apps which use /etc/update-manager/meta-release to check for new releases. It has a unique URL added for the install so we can count the installs.

https://github.com/apachelogger/neon-install-counter is some code to read the web logs and publish a rest api thing

I'd like a nice pretty website with graphs and charts showing the number of installs

anyway something needs access to the web logs

sitter updated the task description. (Show Details)Aug 22 2016, 11:33 AM
sitter updated the task description. (Show Details)
sitter added a subscriber: bcooksley.

packaging.neon now moved. mail sent to list with further information.

releases.neon still needs figuring out where to put I think @bcooksley ?

Yes, we still have to sort something else out for that.

As you need to log query parameters, may I suggest something in lightweight PHP / Python which dumps the needed info in an appropriate form into a database? This would be fairly easy for us to run and as a bonus could run the web frontend / API requirements as well off the same system.

Restricted Application added a subscriber: sysadmin. · View Herald TranscriptAug 23 2016, 10:02 AM

Yeah, I wouldn't block on the log nonesense though. If we get the static files migrated and do simple static file hosting for now, that's good enough for me. @jriddell can have a look at reasonable ways to log at a later point.

Okay. The easiest way for us to run a basic static file served site is by having it's contents on a git repository on git.kde.org. The server will autoupdate when pushes are made.

Could we organise to migrate the contents of the repository?

bcooksley removed a subscriber: sysadmin.

I've now sorted out releases.neon.kde.org on IRC.
That completes everything needed from Sysadmin here I think?

Will open new ticket about releases logs for stats purposes

needs .uk domains changed to cnames, I'll do that shortly

jriddell closed this task as Resolved.Sep 5 2016, 9:55 AM