fix missing mods directory that breaks installation+discussion
Succeeded in starting Wagn like this:
- created directory local/mods manually
- env STATIC_ASSETS=true bundle exec rails server
The passenger error is related to wrong permissions on the files, and is not something which the core Wagn team needs to take action upon.
I have described solutions for some problems I've encountered in my blogpost here:
http://www.two-drifters.com/?p=21
(including advice on the permissions to set, and how to set up memcached).
My wagn insallation works for me right now, please consider this problem solved - maybe adding the directory local/mods to the GitHUB Repository would be a good idea, though.
Thank you for releasing such a cool piece of software.
- Max
Leaving this open for the core team to acknowledge my suggestion to add the directory local/mods.
Maybe give the ticket a better name related to the suggestions?
Something should create the local/mods directory automatically. Probably should be the rake install task (I didn't see if you had used that, it may do that already, should do it if it doesn't).
There are some existing Wagn cards on this site with support information for various platforms. We can integrate this information there as needed.
Hi Max / p13g. Thanks for submitting this and documenting the problem so well. I apologize for the slow response; I've been away from work for the holidays.
I will make sure this issue gets fixed in the next release. (It should probably not require the directory at all.)
Gerry, you may have figured this out, but the prompt for "name" is very confusing in the context of creating a support ticket. Many folks have done just what Max did and used their own name their rather than the "name" of the issue. We need to make this configurable; I see it causing problems all the time.
Right, I hadn't thought of that. Perhaps just "Cardname"?
Yes, that's exactly what confused me :-)
Also there's no possibility to comment more than once without having an account apparently (?), so I set up the account pi3g, because "Max" was already taken by my support ticket ....
I'll have to look into this only-one-comment issue. Definitely not supposed to be that way.
If you want, now that this support ticket has been renamed, you can go to edit > name on pi3g and change your name to "Max".
"Cardname" is worse, imo, Gerry. Most casual contributors to wagn-based sites will have no idea what a card is and shouldn't have to learn. The word "card" should only ever appear in Wagneer space.
I think the key is to make it configurable, because context matters. Sometimes the name is a title, sometimes it's a headline, sometimes it's a one-liner...
fix will be out in 1.12.6