Home/ Questions/Q 4020388
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T10:13:19+00:00

I am trying to push a brand new, empty Rail 3.0.4 project to GitHub,

  • 0

I am trying to push a brand new, empty Rail 3.0.4 project to GitHub, but just realize that the cookie session store has a secret key:

In config/initializers/secret_token.rb

NewRuby192Rails304Proj::Application.config.secret_token = '22e8...'

So how can we avoid it being push to GitHub? We can ignore this file (using .gitignore), but without this file, a Rails app won’t run at all (and is not a complete Rails app). Or in general, other files or frameworks may have files containing secret keys too. In such case, how should it be handled when pushing to GitHub?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Add in your repo:

    • a template of it (secret_token.rb.template),
    • a script able to generate a proper config file secret_token.rb based on local data found on the server (like an encrypted file with the secret value ready to be decoded and put in the secret_token.rb file)

    From there, add a git attribute custom driver:

    enter image description here

    The script referenced above will be your ‘smudge‘ script which will, on checkout of the working tree, generate automatically the right file.

    • 0