Install script for linking/unlinking engines
Reported by Sven Fuchs | March 10th, 2009 @ 09:44 PM
We're at a point where we can start trying out adva-cms with different engines installed.
The easiest way to go could be to just continue to ship all engines and plugins and then allow the user to "activate" them by symlinking (*nix systems) or copying (windows) them to vendor/plugins.
This setup script should support:
- activate all
- activate a, b, c
- deactivate all
- deactivate a, b, c
Obviously necessary core engines would always be and stay linked/activated.
Comments and changes to this ticket
-
Marko Seppä June 18th, 2009 @ 12:34 PM
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<p>Cutting edge cms, blog, wiki, forum ... plattform.</p>
<p>Find the code on <a href="http://github.com/svenfuchs/adva_cms/tree/master">GitHub: adva cms</a></p>
<p>Part of the business application framework <a href="http://www.advabest.org/">adva best</a>.</p>
Marko Seppä
Sven Fuchs