Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data resolver and fetcher #29

Open
marianoguerra opened this issue Jan 20, 2014 · 0 comments
Open

data resolver and fetcher #29

marianoguerra opened this issue Jan 20, 2014 · 0 comments
Labels
Milestone

Comments

@marianoguerra
Copy link
Member

for libs, templates, dependencies, projects a way to search fetch and store those components is needed.

I think a generic API with implementations for stuff like github and bitbucket (to start with) should be useful.

the idea is to have a list of places to search and then look on those paths for project.pbt files or for recursive path lists (for example one repo is a list of folders where heach is a template).

then the ability to fetch and store if needed, for example, for a plugin it will fetch it and put it on the plugin folder of pbt, for templates in the template folder and so on.

this functionality should be reusable and extensible, for example

pbt search plugin foo
pbt search template foo
pbt search project foo

where the name after search can be registered in the search command, and then

pbt install plugin foo
pbt install template foo

to fetch it and store it locally on the place it should go.

in the long term we should play nice with exprire headers, etags, project.pbt versions and similar things to avoid fetching everything every time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants