Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a guide on deploying Yesod to Heroku. #42

Merged
merged 1 commit into from Apr 13, 2019

Conversation

Projects
None yet
3 participants
@StevenXL
Copy link
Member

StevenXL commented Aug 29, 2018

No description provided.

@bitemyapp

This comment has been minimized.

Copy link
Contributor

bitemyapp commented Aug 29, 2018

You've exercised all this recently? My main hesitation w/ Heroku would be that this is docs that can fall out of date easily with no CI feedback. I also had the impression that people weren't paying as much attention to Heroku of late, but that could be a self-selected niche I inhabit.

@StevenXL

This comment has been minimized.

Copy link
Member Author

StevenXL commented Aug 30, 2018

Hi Chris -

Yes, I exercised all of this in the past 2 weeks. I have an app running in production based off of these directions, and the post is as much for others to consume as for me to not forget the details.

I would hate to put something out there that wastes someone's time if things were to break. Would your concern be alleviated if I put the scaffolded site up onto a few heroku dyno, and added CI to that. (Note that I don't know what steps constitute "add CI to that", but I'm willing to learn).

Let me know.

@psibi

This comment has been minimized.

Copy link
Member

psibi commented Dec 30, 2018

@bitemyapp I think this is good to have it even if it becomes a little outdated. I will go ahead and merge if you don' have any concern.

@psibi psibi merged commit 3d4713d into yesodweb:master Apr 13, 2019

@psibi

This comment has been minimized.

Copy link
Member

psibi commented Apr 13, 2019

@bitemyapp I have gone ahead and merged this as I feel it's good to have this even it becomes outdated. It would be easy for others to improve an existing broken documentation rather having no documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.