Skip to content

Road Map #19

@reconbot

Description

@reconbot

We have a few different parts of the project.

  • The cross compiler: takes a package and version and produces a tarball of the package with a .node compiled to run on the tessel. Current status: Works for some packages and not others.
  • The package service. Current status: Using amazon s3, it's great.
  • The status service: Listens to npm for new publishing and determines if it's a package we care about and if we've got a build
  • The build service - automatically builds packages to work on the tessel as the status service discovers them, and stores them on the package service.
  • The test service? - tries to require packages that are cross built on arm hardware to see if they actually work and/or their tests pass.

I have a branch npm-feed where I started a spike of the status service. All of this is up for review and change. If you've got a different idea you'd like to try to get the job done, lets take a look at that too.

cc @soldair

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions