# Looking for system admin help for the package system

**URL:** <https://racket.discourse.group/t/looking-for-system-admin-help-for-the-package-system/375>\
**Category:** General\
**Created:** [December 7, 2021, 8:32pm UTC](https://racket.discourse.group/t/looking-for-system-admin-help-for-the-package-system/375 "2021-12-07T20:32:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![samth](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/samth/32/3_2.png) [@samth](https://racket.discourse.group/u/samth)\
**Post date:** [December 7, 2021, 8:32pm UTC](https://racket.discourse.group/t/looking-for-system-admin-help-for-the-package-system/375/1 "2021-12-07T20:32:20Z")

</div>

Currently, the implementation of [https://pkgs.racket-lang.org](https://pkgs.racket-lang.org) as well as [https://pkg-build.racket-lang.org](https://pkg-build.racket-lang.org) (see Notes) is primarily maintained by Matthew Flatt, although much of it was originally written by Jay McCarthy and Tony Garnock-Jones (for pkgs in particular). Matthew of course wears a lot of hats and maintains lots of things, and he's tired of this job.

As a result, I'm going to take over the sysadmin role, but I'm looking for additional people who can help out as well -- this is a key part of Racket infrastructure and one person is probably not enough. Anyone with experience with system admin, web servers, the Racket web server, AWS, Docker, etc would be great, or but expertise is _not_ required, just a willingness to help out.

Of course, there are many ways to improve the system as well, and helping to maintain it is a great way to get started on that.

If you're willing to volunteer some time to help with this, let me know, either by replying or by messaging me (@samth) here or on Discord or Slack.

### Notes:

The implementation of [pkgs.racket-lang.org](http://pkgs.racket-lang.org) is a front-end here: [GitHub - racket/racket-pkg-website: A frontend for the Racket Package Catalog.](https://github.com/racket/racket-pkg-website) and a backend here: [GitHub - racket/pkg-index](https://github.com/racket/pkg-index/). They both run on the same EC2 instance, and store almost all of the state (including the index of packages) in S3.

The implementation of [pkg-build.racket-lang.org](http://pkg-build.racket-lang.org) is a separate continously-running EC2 instance running the `pkg-build` package, implemented here: [GitHub - racket/pkg-build](https://github.com/racket/pkg-build)