Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8326497
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T00:46:50+00:00 2026-06-09T00:46:50+00:00

I have a Ruby on Rails application which I cloned from a Git repo.

  • 0

I have a Ruby on Rails application which I cloned from a Git repo. It requires a login to do anything, such as register a new user. There are currently no registered users so I see myself as completely locked out

I know the users are stored in a table called users but the underlying database is MySQL and I don’t know how to access the database of a Ruby on Rails application.

Does anyone know how I would go about adding a user?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T00:46:53+00:00Added an answer on June 9, 2026 at 12:46 am

    This is quite a ‘classic’ problem and the immediate thought (“just do it mySQL”) doesn’t work here because of the need to have the rails piece that encodes a password that is entered.
    So you need to actually use rails, something like this (this should all be happening in your local development environment which is the default when working locally):

    You need to create a user.

    Try this:

    cd the_root_of_the_project

    script/rails console
    
    > User.create(:username => 'admin', 
      :password => 'abc123', 
      :password_confirmation => 'abc123') 
      # Add other fields, such as first_name, last_name, etc. 
      # as required by the user model validators.
      # Perhaps :admin => true
    

    This assumes a few things (so change as required) such as an authentication system such as authLogic or devise, attribute and field names, etc, but you should be able to adjust to your needs. You can determine what these are by looking at a few things, specifically the database migration files in db/migrate, the model validations in user/model/user, any existing “seeds” filew for users in db/seeds.rb and the authentication system hooks.

    As to ‘where’ to do this – obviously the console works but you might also want to use the seeds file for this. Whatever ‘create’ command you use in the console can be placed in here, then run with rake db:seed. The downside is that if you check this file into source control it’s less secure. The seeds file is really useful for other tasks such as creating reference tables, initial categories, etc.

    If you don’t have the database actually created at all yet, you’ll need to be aware of and use these tasks:

    rake db:create 
    # as it sounds, creates a database (but no application tables or columns), 
    # using the config/database.yml file for the connection info.
    
    rake db:migrate 
    # Creates tables and columns using the db/migrate/ files.
    
    rake db:seed 
    # Runs commands in db/seeds.rb to create initial records for the application.
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have created a blog application using Ruby on Rails which includes the ability
I have built a very simple blog application using Ruby on Rails. New to
I have a Ruby on Rails application that I'm developing on my computer, which
At the moment I have a Ruby on Rails application which maintains my Users,
I have an Ruby on Rails 3 Heroku application, which needs to perform text
I am writing ruby on rails application, which will have 2 different users types
I have Ruby on Rails application which is using MySQL database. For now I'm
I've created a Ruby on Rails application in which users can login and logout,
I have a ruby on rails 3.0 application which will need a database containing
I have a ruby-on-rails application, which shows a modal dialog form for first-time users.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.