Closed (fixed)
Project:
ELMS
Version:
6.x-1.0-alpha5
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2011 at 17:25 UTC
Updated:
15 Nov 2011 at 17:10 UTC
I was excited that ELMS was on github so I cloned to my Aegir server to test, but I had forgotten that ELMS uses a database import to install :( so it didn't install properly with Aegir.
It would be great to move this to a profiler style installation profile. It's pretty easy to create dummy content on installation too. What's the issue that you still use a database dump?
Comments
Comment #1
btopro commentedhonestly, more important things to do upon getting this whole thing off the ground. I'm in the midst of transitioning to a real installer. First step is getting everything into features which I more or less have. Then it's taking my massive code-dump modules like elms_helper and elms_spaces and creating actual compartmentalized things so that elms_core directory is very small and elms_features/ is more prominent. working on og_clone (which is almost working) and then back to a real installer most likely.
Comment #2
markwk commentedGot it! Makes sense to me. Once the features are working as they should, building a profile shouldn't be a problem at all. (Sorry if it sounded like I was complaining just noting ;-)
Comment #3
btopro commentednp, been asked that a lot. it's a very dev specific problem and i've been heavily focused on UX. I'll get there, just got cloning rigged up :)
Comment #4
btopro commented