FATAL: role "prelaunch" does not exist

[emilepetrone]

trafficstars

Thanks for doing this - I wish I had found this repo sooner! One question, when I just ran the setup, the DB failed until I commented out the user/password in the Test & Development db's in database.yml. Any ideas?

[Techofficer]

Hi, the problem relates to your PostgreSQL database configuration - "prelaunch" user does not exist there simply because it was never created before. You can replace "prelaunch" user in config.yml to any user already existing in your database, or you can create a new one.

[aarhusgregersen]

Hey I actually have a similar problem. For me whenever I add data to the seed it won't save the (user)data. So even though I edited the seeds file it won't add my user to my database. Thoughts?

EDIT: FIXED. Turned out I was having too short a password and the login page AND the console doesn't give usefull errors, so I had to look up the devise initializer to see if password lengths were set.

[mcconnell113]

I'm so stuck on this part. Any additional guidance? I've been fumbling around on this one for over an hour now. Thanks in advance. Edit I've opened the database.yml file what now?

[aarhusgregersen]

What I've found works with this gem is usually change the database.yml to the following content:

default: &default
  adapter: sqlite3
  encoding: unicode
  pool: 5

development:
  <<: *default
  database: prelaunchr_development
  username: prelaunch
  password: password

Warning: The database defined as "test" will be erased and
re-generated from your development database when you run "rake".
Do not set this db to the same as development or production.
test:
  <<: *default
  database: travis_ci_test
  username: postgres


production:
  adapter: postgresql
  database: prelaunchr_production
  username: deployer
  password: prelaunch
  encoding: unicode
  pool: 5

`

This way the pg db uses the same login information (which really isn't nessecary anyway), and you can develop with sqlite, which is a lot more straight forward.

[mcconnell113]

Hey thanks for your post. I think I got it to work right at the same time as you posted. I finally see the prelauncher page on localhost:3000 so i think I won.

[aarhusgregersen]

Please let me know if you have further issus. I've gotten pretty good at working with this gem.

[mcconnell113]

I appreciate your generous help I'll let you know if I have any other hiccups. Im just happy that i see a site localhost.

[mcconnell113]

This is the next thing that I'm hung up on and it looks as if the rest will be easy. when i do this step Go to localhost:3000/admins/sign_in and log in with Admin user credentials

I tried to use my credentials that I added into seed.rb and also tried to see if it was supposed to use something out of the database.yml The only thing that makes sense to me would be to use the seed.rb credentials but that's not working for me. Am I supposed to something to the seed.rb file further to get this to work or am I overlooking something else perhaps?

[Techofficer]

Go to the root directory of your rails project and try the following code bundle exec rake db:seed Alternatively, you can log in to your rails console bundle exec rails console add a new admin there: Admin.create(email: "YOUR@EMAIL", password: "YOUR_PASSWORD") and then login with these credentials on http://localhost:3000/admins/sign_in page

[mcconnell113]

Thank you very much!

[mcconnell113]

I hate to keep being a bother. I've got it 100 percent working on localhost:3000 however I've tried for a good portion of the day to deploy this to heroku so that i can then use a subdomain for my website to point to it. I either get one of two things when I attempt to deploy. I get If you are the application owner check the logs for more information. but I'm still unsure how to check any logs. Im deployed at https://saplinglaunch.herokuapp.com/ or i'll get what seems to me like a blank heroku app being deployed that isn't pushing anything up to heroku. It seems that the one that says to check my logs suggests that I've deployed correctly but perhaps something isn't set up for production correctly. I also just got an email from mailchimp that says my api key was deactivated because it was showing in the repo. Can i deflect this simply by making the repo private or is there another way I need to go about this? Sorry again for the zillion questions. I'm new to ruby on rails and this seemed like something fun and useful I could play with and utilize.

[Techofficer]

To see heroku logs, go to the root directory of your rails project and type: heroku logs Regarding mailchimp, privare repo should work for you