I have a new version of the TurboGears site I've spent the last five
years of my life on. :)
I'm just about to launch it, but I'd like to get some more feedback
from friends and family before I do.
I was thinking I'd keep the old site up and add the new site under a
separate DNS entry. So I could tell people to go to http://new.1000corks.com instead of just http://1000corks.com
But, and here is where it gets complicated, I'd like anyone going to
the new site to have to enter a beta password before they can access
it. There will be just one beta password for the new site, not one
per person. There are a lot of different urls they could enter the
site from.
How can I make that possible, without manually hacking each exposed
function/page?
On Wed, Oct 17, 2012 at 3:40 PM, Sam <samsli...@gmail.com> wrote:
> I have a new version of the TurboGears site I've spent the last five
> years of my life on. :)
> I'm just about to launch it, but I'd like to get some more feedback
> from friends and family before I do.
> I was thinking I'd keep the old site up and add the new site under a
> separate DNS entry. So I could tell people to go to http://new.1000corks.com > instead of just http://1000corks.com
> But, and here is where it gets complicated, I'd like anyone going to
> the new site to have to enter a beta password before they can access
> it. There will be just one beta password for the new site, not one
> per person. There are a lot of different urls they could enter the
> site from.
> How can I make that possible, without manually hacking each exposed
> function/page?
> Thanks!
> --
> You received this message because you are subscribed to the Google Groups "TurboGears" group.
> To post to this group, send email to turbogears@googlegroups.com.
> To unsubscribe from this group, send email to turbogears+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
On Wednesday, October 17, 2012 12:48:18 PM UTC-7, Michael Pedersen wrote:
> Put it behind an Apache proxy, and have Apache request the beta > password. Quickest and easiest way I can think of.
> On Wed, Oct 17, 2012 at 3:40 PM, Sam <sams...@gmail.com <javascript:>> > wrote: > > I have a new version of the TurboGears site I've spent the last five > > years of my life on. :)
> > I'm just about to launch it, but I'd like to get some more feedback > > from friends and family before I do.
> > I was thinking I'd keep the old site up and add the new site under a > > separate DNS entry. So I could tell people to go to > http://new.1000corks.com > > instead of just http://1000corks.com
> > But, and here is where it gets complicated, I'd like anyone going to > > the new site to have to enter a beta password before they can access > > it. There will be just one beta password for the new site, not one > > per person. There are a lot of different urls they could enter the > > site from.
> > How can I make that possible, without manually hacking each exposed > > function/page?
> > Thanks!
> > -- > > You received this message because you are subscribed to the Google > Groups "TurboGears" group. > > To post to this group, send email to turbo...@googlegroups.com<javascript:>.
> > To unsubscribe from this group, send email to > turbogears+...@googlegroups.com <javascript:>. > > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en.
> That works great! I don't know why I didn't think of it.
> Thank you.
> On Wednesday, October 17, 2012 12:48:18 PM UTC-7, Michael Pedersen wrote:
> > Put it behind an Apache proxy, and have Apache request the beta
> > password. Quickest and easiest way I can think of.
> > On Wed, Oct 17, 2012 at 3:40 PM, Sam <sams...@gmail.com <javascript:>>
> > wrote:
> > > I have a new version of the TurboGears site I've spent the last five
> > > years of my life on. :)
> > > I'm just about to launch it, but I'd like to get some more feedback
> > > from friends and family before I do.
> > > I was thinking I'd keep the old site up and add the new site under a
> > > separate DNS entry. So I could tell people to go to
> >http://new.1000corks.com > > > instead of justhttp://1000corks.com
> > > But, and here is where it gets complicated, I'd like anyone going to
> > > the new site to have to enter a beta password before they can access
> > > it. There will be just one beta password for the new site, not one
> > > per person. There are a lot of different urls they could enter the
> > > site from.
> > > How can I make that possible, without manually hacking each exposed
> > > function/page?
> > > Thanks!
> > > --
> > > You received this message because you are subscribed to the Google
> > Groups "TurboGears" group.
> > > To post to this group, send email to turbo...@googlegroups.com<javascript:>.
> > > To unsubscribe from this group, send email to
> > turbogears+...@googlegroups.com <javascript:>.
> > > For more options, visit this group at
> >http://groups.google.com/group/turbogears?hl=en.
> no worries sam, that happens to the best of us. :)
> if i may, why are you still using tg 1.5?
> also congratulations on the new release!
> On Oct 18, 8:04 am, Sam <samsli...@gmail.com> wrote:
>> Michael....
>> That works great! I don't know why I didn't think of it.
>> Thank you.
>> On Wednesday, October 17, 2012 12:48:18 PM UTC-7, Michael Pedersen wrote:
>>> Put it behind an Apache proxy, and have Apache request the beta
>>> password. Quickest and easiest way I can think of.
>>> On Wed, Oct 17, 2012 at 3:40 PM, Sam <sams...@gmail.com <javascript:>>
>>> wrote:
>>>> I have a new version of the TurboGears site I've spent the last five
>>>> years of my life on. :)
>>>> I'm just about to launch it, but I'd like to get some more feedback
>>>> from friends and family before I do.
>>>> I was thinking I'd keep the old site up and add the new site under a
>>>> separate DNS entry. So I could tell people to go to
>>> http://new.1000corks.com >>>> instead of justhttp://1000corks.com
>>>> But, and here is where it gets complicated, I'd like anyone going to
>>>> the new site to have to enter a beta password before they can access
>>>> it. There will be just one beta password for the new site, not one
>>>> per person. There are a lot of different urls they could enter the
>>>> site from.
>>>> How can I make that possible, without manually hacking each exposed
>>>> function/page?
>>>> Thanks!
>>>> --
>>>> You received this message because you are subscribed to the Google
>>> Groups "TurboGears" group.
>>>> To post to this group, send email to turbo...@googlegroups.com<javascript:>.
>>>> To unsubscribe from this group, send email to
>>> turbogears+...@googlegroups.com <javascript:>.
>>>> For more options, visit this group at
>>> http://groups.google.com/group/turbogears?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "TurboGears" group.
> To post to this group, send email to turbogears@googlegroups.com.
> To unsubscribe from this group, send email to turbogears+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
That's a really good question. There are a bunch of reasons, including it's a pretty complex project. So I'd rather port it to something else at the same time I port it to Python 3.x, and get through all the pain at once.
And, although I'm sure TG 2.x is better, TG 1.x is pretty nice. I've had the opportunity to recently work on Django, Pyramid, and Flask projects, and TG 1.5 still has lots of charm.
Once TG supports Python 3.x I'll probably make the transition. In the meantime the framework still works really well for me. I can't think of anything I'm missing. Although I still have to hack up the redirect function every once in a while to make it do what I need it to. ;)
On Thursday, October 18, 2012 5:45:35 PM UTC-7, Mengu wrote:
> no worries sam, that happens to the best of us. :)
> if i may, why are you still using tg 1.5?
> also congratulations on the new release!
> On Oct 18, 8:04 am, Sam <samsli...@gmail.com> wrote: > > Michael....
> > That works great! I don't know why I didn't think of it.
> > Thank you.
> > On Wednesday, October 17, 2012 12:48:18 PM UTC-7, Michael Pedersen > wrote:
> > > Put it behind an Apache proxy, and have Apache request the beta > > > password. Quickest and easiest way I can think of.
> > > On Wed, Oct 17, 2012 at 3:40 PM, Sam <sams...@gmail.com<javascript:>> > > > wrote: > > > > I have a new version of the TurboGears site I've spent the last five > > > > years of my life on. :)
> > > > I'm just about to launch it, but I'd like to get some more feedback > > > > from friends and family before I do.
> > > > I was thinking I'd keep the old site up and add the new site under a > > > > separate DNS entry. So I could tell people to go to > > >http://new.1000corks.com > > > > instead of justhttp://1000corks.com
> > > > But, and here is where it gets complicated, I'd like anyone going to > > > > the new site to have to enter a beta password before they can access > > > > it. There will be just one beta password for the new site, not one > > > > per person. There are a lot of different urls they could enter the > > > > site from.
> > > > How can I make that possible, without manually hacking each exposed > > > > function/page?
> > > > Thanks!
> > > > -- > > > > You received this message because you are subscribed to the Google > > > Groups "TurboGears" group. > > > > To post to this group, send email to turbo...@googlegroups.com<javascript:>.
> > > > To unsubscribe from this group, send email to > > > turbogears+...@googlegroups.com <javascript:>. > > > > For more options, visit this group at > > >http://groups.google.com/group/turbogears?hl=en.
