Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #9668

Closed
Open
Created Sep 04, 2013 by Ximin Luo@infinity0

restructure flashproxy source tree

The source tree has quite a messy structure that makes it hard to write a coherent install script, e.g. for debian packaging. I propose something like the following:

Top-level

renamed: doc/design.txt -> design.txt

client

renamed: Makefile -> client/Makefile

renamed: doc/flashproxy-$$ -> client/doc/flashproxy-$$

renamed: flashproxy-$$ -> client/flashproxy-$$

renamed: setup.py -> client/setup.py

renamed: torrc -> client/torrc

facilitator

renamed: doc/facilitator-howto.txt -> facilitator/doc/facilitator-howto.txt

renamed: doc/appengine-howto.txt -> facilitator/doc/appengine-howto.txt

renamed: doc/gmail-setup.txt -> facilitator/doc/gmail-setup.txt

renamed: appengine/$$ -> facilitator/appengine/$$

websocket-transport

renamed: doc/websocket-transport.txt -> websocket-transport/doc

proxy

renamed: modules/$$ -> proxy/modules/$$

/websocket-transport.txt

plus the necessary adjustments (paths etc) to make everything work again.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking