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

Deployment: "Our recommended PaaS services" should match the one in the NodeJS section #28862

Closed
3 tasks done
DrantDumani opened this issue Sep 25, 2024 · 6 comments · Fixed by #29148
Closed
3 tasks done
Labels
Status: Stale This issue/PR has been inactive for over 30 days and will be closed if inactivity continues

Comments

@DrantDumani
Copy link
Member

Checks

Describe your suggestion

The Our recommended PaaS services segment in the NodeJS path has received several updates over time to remove options that have no longer offer free services (such as Heroku and Fly.io). The lesson has also been updated to include more options that can be used to host databases for free.

The Ruby on Rails version of the lesson still mentions Heroku and Fly.io. It also lacks the aforementioned database options that the NodeJS path lesson talks about.

As a proposed solution, the "Our recommended PaaS services" segment should be updated to match that of the NodeJS path.

Path

Ruby / Rails

Lesson Url

https://www.theodinproject.com/lessons/ruby-on-rails-deployment

(Optional) Discord Name

Elemeandor

(Optional) Additional Comments

No response

@KevinMulhern
Copy link
Member

Thanks for the suggestion @DrantDumani. I agree that Koyeb, and Neon would be worth including, both of those have seem to have decent guides for Rails.

But I'd be hesitant to remove Fly.io and Heroku from the options. The intention of this lesson wasn't to only include options with free plans (although that is a big plus), but what services were easiest to get up and running with. I think both Heroku and Fly still probably have the best DX out of all the available PaaS options available.

@MaoShizhong
Copy link
Contributor

MaoShizhong commented Sep 27, 2024

Related: #28491

Fly and Adaptable (as well as Heroku at the time of milestone release) were removed from the Node version because we weren't comfortable with the idea of recommending paid-only services in the section following the lesson wording:

Choosing a PaaS provider was once a simple decision. Heroku had a free tier that gave you everything needed to host as many small apps as you wanted, but they unfortunately discontinued it in 2022.

Luckily, there are still plenty of other great options out there. The downside is that they all have very limited free tiers. For this reason, and to accommodate as many of our learners as possible, we’re going to recommend a range of options instead of just one.

And it goes on to say how the options below allow for free hosting, but if people are happy to pay, you get more options and features of course.

But that was for the Node side only. I didn't want to make the same decision for the Rails side of things as well.

Copy link

This issue is stale because it has had no activity for the last 30 days.

@github-actions github-actions bot added the Status: Stale This issue/PR has been inactive for over 30 days and will be closed if inactivity continues label Oct 28, 2024
@JoshDevHub
Copy link
Contributor

@DrantDumani Do you still have an interest in working on this?

I agree with Kevin that I don't think I'd want Fly or (especially) Heroku removed from the Rails deployment guide, but I do think some of the ones that have been added to the Node deployment guide could be good to have. Would definitely welcome a PR that added Koyeb and Neon as options for learners to use. Let me know if you want to work on it.

@DrantDumani
Copy link
Member Author

@JoshDevHub yeah, I'd be down to add those options to the Rails deployment lesson.

@github-actions github-actions bot removed the Status: Stale This issue/PR has been inactive for over 30 days and will be closed if inactivity continues label Nov 26, 2024
Copy link

This issue is stale because it has had no activity for the last 30 days.

@github-actions github-actions bot added the Status: Stale This issue/PR has been inactive for over 30 days and will be closed if inactivity continues label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale This issue/PR has been inactive for over 30 days and will be closed if inactivity continues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants