Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDocument how to distribute and import projects #190
Comments
mnp
changed the title
|
A nice feature of other project 'init' systems is to have a command akin to 'npm init' which will minimally generate the needed metadata files (in recent years it's gotten a nice wizard to assist in this process). I agree with the op, if you already have a project that exists in the form of an app.js, it would be nice perhaps to offer a command like: chalice new-project --init , and this would add any needed metadata files if they do not exist, and would balk at overwriting any existing files without the user's permission. Containing directory could simply become the name of the project, or prompt the user for a name. |
|
@mnp - Thanks for raising this issue. I spent a few hours last night trying to figure out the best way to accomplish this. Your process seems like the best way to do this currently. I like @truedat101's recommendation. In addition to metadeta, I think having a mechanism to download Amazon Linux wheels would simplify development for developers on platforms that are not binary-compatible with Amazon Linux. |
Creating a new project from scratch is obvious, but if an author wished to post his Chalice project for other developers to use, it's less so. I'm guessing the best practice would be:
app.pyfor your projectfoo.chalice new-project fooapp.pywith the sharedapp.pycd foo && chalice deployIs this correct and is it what's intended? It's straightforward but perhaps indirect. Please throw a paragraph in the README.