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

Extensions directory #121

Closed
kariemil opened this issue Jun 30, 2014 · 4 comments
Closed

Extensions directory #121

kariemil opened this issue Jun 30, 2014 · 4 comments

Comments

@kariemil
Copy link

I find the /extensions directory a bit bothersome. As far as I am concerned, as a minimally technical user of Stacey, it is a do-not-touch zone. I like the idea that the /app directory being the only such area. Would it be possible to move /extensions into /app?

@mjau-mjau
Copy link

// me just looking through some threads and commenting

I guess the idea would be that /app is Stacey, and should remain untouched, whereas /extensions could technically be extended- or changed by yourself without affecting Stacey core ...

@kariemil
Copy link
Author

Then why is SLIR in /app?

@mjau-mjau
Copy link

shrugs I don't really see any reason why everything couldn't be inside the /app folder as you suggest, although one could argue that SLIR is an essential part of the Stacey app ... Just the way it is I guess ... ;)

@o-l-e
Copy link

o-l-e commented Nov 12, 2014

i think @kolber's idea was that this was a place where people could create their own extensions/plugins.
So in other words not really a "do-not-touch-zone" like the app-folder.

Ps: close the issue if you agree ;)

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

No branches or pull requests

3 participants