Use a rails application template for Heroku + example-app

[elia]

Description

The current heroku deploy button is partially broken and uses a custom buildpack.
This PR introduces a reusable rails application template that can be used to generate and update a demo-app (presumably published at https://github.com/solidusio/solidus-example-app).

The app will have its own app.json and will be a good base for deploys to heroku, but also
for forks. Heroku deploys should be already on the right path for production use (cache, images, etc.)

The template can also be used as an executable to build the official demo app:

~/Code/solidus $ cd ..
# the default APP_NAME is solidus-example-app
~/Code $ solidus/bin/rails-application-template [APP_NAME]
# …generates the app…

Demo app

The resulting code is available here: https://github.com/nebulab/solidus-example-app
I just had to change the heroku button url to point at the nebulab org instead of solidusio, other than that it's straight out of the template.

See it in action: https://elia-solidus-demo.herokuapp.com

Screenshots

Checklist:

• I have followed Pull Request guidelines
• I have added a detailed description into each commit message
• I have updated Guides and README accordingly to this change (if needed)
• I have added tests to cover this change (if needed)

[ericsaupe]

Looks good to me. This does make some assumptions as to services like Cloudinary and Memcachier but since this is meant as an example app I think those are fine choices that are easily changed by the user.

[tvdeyen]

Thanks.

[jacobherrington]

Nothing blocking, just a small typo.

I think this is a fine option. Thanks for the work @elia!

[jacobherrington]

I wasn't sure about using --force here without asking the user for confirmation, but I talked myself into being okay with it.

[elia]

The idea is to have something that can be automated and requires as few interaction as possible. That's only for the chore of updating the example app after a release of course, it doesn't happen when used as an app template.

[jacobherrington]

Yes, and worst case scenario we just regenerate the example app. The repo we are pushing to will not contain anything we would be afraid to lose.

[elia]

Looks good to me. This does make some assumptions as to services like Cloudinary and Memcachier but since this is meant as an example app I think those are fine choices that are easily changed by the user.

Yes, given it's going to be deployed on heroku I looked for services that had a free tier and were at the same time viable for production use (using a cache and a CDN are both very good practices for any production store).

[kennyadsl]

@elia I moved the repo from nebulab org to solidusio: https://github.com/solidusio/solidus-example-app

Are we good to go?

[elia]

Are we good to go?

I'll remove the last commit and we're good! 🚀

[elia]

@kennyadsl done, and also regenerated the app to with the solidusio heroku button link 👍