Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #1392 (closed enhancement: wontfix)

Opened 12 years ago

Last modified 10 years ago

Implement "tg-admin serve"

Reported by: alberto Owned by: anonymous
Priority: normal Milestone: 1.5
Component: TurboGears Version:
Severity: normal Keywords: tg-admin


Add a new command to tg-admin to start up a TG app without the need of start-myapp.py.

This command should expose "paster serve"'s interface but be clever enough so that, when called inside an egg dir when developing, it can automatically boot the current app with no arguments or deployment config.

The command should also be able to receive a deployment config file as parameter to start up arbitrary paste.deployable apps.

Some examples:

tg-admin serve

Serves the app in the current directory (which should be a TG project)

tg-admin serve --reload

Same as the above but turns automatic reloading on (maybe enable by default in config-less mode since it is assumed to be used in dev. mode?)

tg-admin serve myapp.ini

Default way to start up a TG app from a deployment config. This command can be used in supervisord scripts, init.d scripts, etc... on a production site.

tg-admin serve --egg MySuperBlog prod.cfg

Refers to an app's egg and serves it using the specified TG-style config. An alternative way to boot an app which doesn't require a deployment config.

More syntax suggestions welcomed :)

This ticket is really easy to implement by someone familiar with tg.admin commands internals since it's a thin wrapper around "paster serve". Good food for sprint.


Change History

comment:1 Changed 12 years ago by alberto

  • Keywords tg-admin sprint added

comment:2 Changed 12 years ago by elvelind

tg-admin already accepts --egg/-e and --config/-c as options so those would be free (tg-admin -e MyBlog? -c prod.cfg serve )

comment:3 Changed 12 years ago by Chris Arndt

  • Type changed from defect to enhancement

Changeset r3776 implements the start script as a console script entry point. This automates handling of the start script and also makes it possible to have several start scripts for different versions of a project.

Or, wait. Is this meant for TG 2.x? Then the milestonefor this ticket is not not correctly.

comment:4 Changed 12 years ago by Chris Arndt

/not not/not set/

comment:5 Changed 12 years ago by Chris Arndt

  • Version trunk deleted

comment:6 Changed 11 years ago by faide

  • Milestone changed from 1.1 to 1.1.1

comment:7 Changed 11 years ago by faide

  • Milestone changed from 1.6 to 1.5

comment:8 Changed 11 years ago by mramm

  • Keywords sprint removed

comment:9 Changed 10 years ago by Chris Arndt

  • Status changed from new to closed
  • Resolution set to wontfix

apparently nobody was interested in implementing this and with the command module in quickstart I don't see a need for this.

Note: See TracTickets for help on using tickets.