"bundle exec rake heroku" throws up further configuration options

alagu / pagoda

Zen-like blogging interface for Jekyll (login: admin/admin)

http://pagoda-demo.herokuapp.com/admin/

MIT License

300 stars 17 forks source link

"bundle exec rake heroku" throws up further configuration options #15

Closed benedfit closed 10 years ago

benedfit commented 11 years ago

Can anyone advise a Heroku n00b with further steps to deploy after running "bundle exec rake heroku"?

alagu commented 11 years ago

Hey benedfit.

It does throw up options. Let me help you with it:

Configuring Heroku for you
Enter your repository url (e.g git@bitbucket.org:alagu/private-blog.git): (1)
Pick a Username: (2)
Enter a password:  (3)******
Heroku configuration Done.
Copy this ssh public key to github or bitbucket or your git remote (also saved in ~/.ssh/pagoda-key.pub)

(4) ssh-rsa  <<rsa-key>>

Visit http://vast-eyrie-3335.herokuapp.com/ and login with the above given Username & Password

You have to enter 3 items.

Your git repository (git@github.com:name/repo.git)
An username to login
Password for the same

Once you are done, you should push it to heroku (git push heroku master)

After that, add (4) to your ssh keys in your repository host (github/bitbucket).

That should be it. Then you can access your blog in the above mentioned URL (you have to add a /admin)!

alagu commented 11 years ago

If you have a specific blog, I can help you set it up.

benedfit commented 11 years ago

Yeah advise on setup would be appreciated. I'm currently set up as follows:

Bitbucket repo that contains folder named source that contains my Jekyll layouts etc, which is generated into a folder called _deploy
The contents of _deploy is then pushed to a Github repo and hosted via Github Pages

How would you advise changing this structure to best work with Pagoda? I'm also a little confused about what is actually pushed to Heroku. Is this just the admin system? Or will my whole site then be running on Heroku?

Cheers

Ben

alagu commented 11 years ago

Hey @benedfit

Your structure is perfect for working with Pagoda, it doesn't need to change at all. Just the admin system is pushed to pagoda. Any changes you make on the admin system would be pushed to your bitbucket instance. So there is nothing stored there.

You could retain your site as is. Currently in between something, I'll get back to you soon on this.

-Alagu

alagu commented 10 years ago

Hey @benedfit, I'm closing this issue - let me know if you need any help with setting it up.