Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Proposal: Automatic Package Compilation

Open
#37 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, flask, python

Research direction

Start with the package compilation steps described in the README and determine what parts of the current process would need automation. Compare the proposed Travis-based workflow with the alternative EC2 listener approach; done would require an agreed design and an automated compilation path for the packages.

Written by the indexing model from the issue text.

Description

In some sense, the package compilation for AWS Lambda it's simple, following some basic steps, described in the README for example, where you should install the package dependencies and then compile, zip, and PR.

It's possible to make this process automatic using a tool like Travis? Otherwise, I can make available an instance on EC2 running the correct AMI to that purposes, where should have some listener (Flask for example) that runs the process.

Dominant language
Shell
Stars
728
Forks
157
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Miserlou/lambda-packages

All issues in Miserlou/lambda-packages

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.