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

make ramen application specific? #14

Open
rip747 opened this issue Jul 17, 2012 · 7 comments
Open

make ramen application specific? #14

rip747 opened this issue Jul 17, 2012 · 7 comments

Comments

@rip747
Copy link

rip747 commented Jul 17, 2012

first off I have to say that this is one really kewl project you all are working on.

what I'm wondering if there are plans to make ramen application specifc. basically declare ramen packages inside the application.cfc of a project sort of like how you can declare gems inside a rails project?

@atuttle
Copy link

atuttle commented Dec 2, 2012

Unfortunately there's no way for us to hook into an Application.cfc and get this information out. If you've got a clever idea, I'm all ears, but short of scanning the file system for all Application.cfc's and then reading and parsing the file (NOT something I want to do), I don't see how it's possible.

@russplaysguitar
Copy link
Member

sounds like you might be interested in https://github.com/foundrycf/foundry

@rip747
Copy link
Author

rip747 commented Dec 2, 2012

@atutle the easiest way I can think of is just declare the ramen object inside the application.cfc like so

<Cfset ramen = createobject("component", "somepth.Ramen").init()>
<cfset ramen,addPackage("Whatever")>

i would also suggest maybe reaching out to the foundry project and see what differences, similarities the two projects bring. you and @joshuairl are two really talented programmers and i'm sure you guys could combine skills to make something awesome for the community.

@jfrux
Copy link

jfrux commented Dec 2, 2012

fpm uses a foundry.json similar to npm's package.json. It is now able to determine dependencies, download and install them to a particular dir (foundry_modules) from the registry / directly from a git repo.

It does this via command prompt with the fpm install.

Also, it has module.cfc that you can extend which allows you to require() other modules directly which operates just like nodes require.

@jfrux
Copy link

jfrux commented Dec 2, 2012

You can also do fpm register to add it to the FPM registry.

@jfrux
Copy link

jfrux commented Dec 2, 2012

I'd love it if we could come up with a joint project effort that could solve this.
:D 👍

@atuttle
Copy link

atuttle commented Dec 2, 2012

Had a poke around the foundrycf org's repo's and it looks like fpm is kind of like what I really wanted when I created Ramen. I sort of settled for something closer to the Railo extension manager. I'd be happy to contribute, but it looks like you're still pretty early-stage with everything. Do you have a sort of roadmap, or an idea for what needs to be working first? Maybe you can show me around what's already working?

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

No branches or pull requests

4 participants