Custom Query (49 matches)

In the main() method in source:OpenWorkouts-git/ow/__init__.py we do some pyramid setup, including setting up a SignedCookieSessionFactory? and AuthTktAuthenticationPolicy? instances. Both require some salt hashes to be provided. Those hashes are right now hardcoded there, while it would be better to put them into the proper .ini files.

Setup a staging env where we can push unfinished code to test before releasing

So, we started working on the project using darcs as the DVCS for the repos. Then we created a git so some people could work on the project and personally I even considered a third option (mercurial as I do prefer that over the other 2).

This lead to a big mess when trying to keep the repos in sync, plus a big headache to me and a not-very-productive discussion about what to do.

So, BDFL style, I decided to go on with:

• use git as the DVCS tool (for now)

• keep the repos in our openworkouts server

• keep using trac for web access to the repos + tickets/tasks/milestones

• have a mirror in github, with a very big WARNING telling users where the main development and repos goes (trac+git on our server)

I'm not fond of git, but right now this is what we will do.

So, for this ticket, we have to:

• remove/delete darcs and mercurial repos

• put the main git repo (under repos/git/OpenWorkouts-current) into repos/OpenWorkouts

• remove the third-party darcs plugin from trac (as this allows us to update trac to the most recent versions)

• update docs, scripts, tickets, etc to point to the git repo