Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

time tracker: think private 'twitter' that counts the duration of status messages.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 app
Octocat-spinner-32 config
Octocat-spinner-32 db
Octocat-spinner-32 lib
Octocat-spinner-32 log
Octocat-spinner-32 public
Octocat-spinner-32 script
Octocat-spinner-32 spec
Octocat-spinner-32 test
Octocat-spinner-32 tmp
Octocat-spinner-32 vendor
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .gitmodules
Octocat-spinner-32 Capfile
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README
Octocat-spinner-32 README.markdown
Octocat-spinner-32 Rakefile
Octocat-spinner-32 agpl.txt
README.markdown

Getting Started in Development

cp config/database.sample.yml config/database.yml
rake gems:install
rake db:create:all db:schema:load

Run the specs:

rake spec

Oh wait, there are massive spec failures. I'll try to hack on that later.

To use at http://localhost:3000/ :

  • Add a user at http://localhost:3000/signup
  • If you don't get a confirmation email (which you likely won't since you don't have the mail sending configured), check log/development.log for a copy of the confirmation email that would have been sent to you, copy and paste the activation url from it into the browser toolbar (should look like the following: http://tt.entp.com/activate/db61f839776898cedee72fcb9f87465d797e2e93 - of course, replace tt.entp.com with your dev server address.

Deploying

To deploy, you need to create the following files (we provide also the default template for those files to get you started):

config/deploy/production.rb

set :rails_env, :production
server 'example.com', :app, :web, :db, :primary => true

config/deploy/staging.rb

set :rails_env, :staging
server 'staging.example.com', :app, :web, :db, :primary => true

config/initializers/custom.rb

TT_HOST  = 'example.com'
TT_EMAIL = 'admin@example.com'
SIGNUPS_ENABLED = false

ActiveSupport::CoreExtensions::Time::Conversions::DATE_FORMATS.update \
 :time => '%I:%M %p'

config/moonshine/production.yml

# production-specific moonshine configuration
#
# You can set anything here that you might normally put in config/moonshine.yml, but will only apply to production

# Primary domain application will be accessed as 
:domain: example.com

# Domain aliases for applaction. One common use of this is for asset hosts.
#:domain_aliases:
#  - assets1.yourapp.com
#  - assets2.yourapp.com

config/moonshine/staging.yml

# staging-specific moonshine configuration
#
# You can set anything here that you might normally put in config/moonshine.yml, but will only apply to staging

# Primary domain application will be accessed as 
:domain: staging.example.com

# Domain aliases for applaction. One common use of this is for asset hosts.
#:domain_aliases:
#  - staging.assets1.yourapp.com
#  - staging.assets2.yourapp.com

Once you've added those files and made changes as appropriate, you should be able to get going and just use regular old moonshine deployment techniques.

Something went wrong with that request. Please try again.