Apache Installation is too complicated
| Reported by: |
sim@… |
Owned by: |
|
|
Priority:
|
normal
|
Milestone:
|
|
|
Component:
|
general
|
Version:
|
|
|
Severity:
|
normal
|
Keywords:
|
needinfo
|
|
Cc:
|
|
Branch:
|
|
|
Release Notes:
|
|
|
API Changes:
|
|
|
Internal Changes:
|
|
The installation of Trac is just way too complicated. It needs to be simplified, especially for the "recommended" way to do it. When I read the instructions for Apache configuration it says to run "deploy" create the WSGI file in /tmp and then copy it back to the instance directories. I think. I can't remember because it is so crazy. Why can't it create those directly if that is the way to do it? Then later it references a different way to run the "deploy" command when setting up the Apache config files. I have installed Trac this before several times and still have to hack my way around without knowing what I am doing.
Change History
(5)
| Resolution: |
→ worksforme
|
| Status: |
new → closed
|
Nobody is trying to make it more complicated than needed. If you see a way to improve it please let us know. Your description is unfortunately a bit vague. Are you suggesting a documentation change? An improvement to
trac-admin deploy? Both might be good ideas.If you are looking for clarifications you should probably ask on the MailingList.
I'm guessing (because you didn't specify) you are talking about the TracInstall#cgi-bin and TracInstall#MappingStaticResources sections. Both mention the
deploycommand, and a good writer could probably simplify the text.Maybe the deploy command without a target directory argument could just deploy to the environment? Or maybe
initenvcould automatically deploy to the created environment directory?