部署Ruby on Rails - Heroku有很好的选择吗？

问题描述

我开始一个新的小企业，一个POC，如果你愿意，我想在某个地方免费部署我的Rails应用程序。
我发现有Heroku，还有其他选择吗？

解决方案

有没有

这是一个非常好的帖子发现主题

I一个接一个地选择了这个选项，而对于一个中小型网站，OpenShift是最好的选择，至少开发和创建一个POC \Prototype

为什么会更好？

• 给你什么Heroku会给你
• 
  
• 它给你本地（持久）的存储 - 所以你不需要支付S3在亚马逊或同等级 - 我想在某种程度上你想这样做（使用S3） ，但至少对于开始，你不需要把钱放在它上面。


• 似乎网站运行速度更快


• 我觉得在控制机器上发生的变化更加灵活

有没有什么缺点？ strong>

• 我在Openshift上找到的唯一缺点是，似乎在Heroku上部署需要更多的时间，而且相当可观第一次在网站上发布延迟（但第一次工作更快 - 如果您认为这是问题，则与浏览器缓存无关）

这可能是本文档下的Gemfile部分可以解决这个问题...我会稍后尝试

为了在Openshift上部署已经存在的应用程序，我需要执行哪些步骤？

在很多地方我找到关于h的解释ow来创建和部署新应用程序，但是要了解如何将已经存在的应用程序放在OpenShift上有点困难。

这是我想解释的原因

假设
- 你的应用程序已经被git控制了
- 它的路径是/ home / dev / MyApp
- 你现在在/ home / dev

1. 在


2. 使用命令行工具，我发现他们更多的信息


3. 转到


4. 按照步骤1..3安装和设置命令行工具


5. cd到您的rails应用程序文件夹/ home / dev / MyApp


6. 创建一个新的应用程序域 - 运行： rhc domain-create< domain name>



7. 在OpenShift中创建应用程序赛跑

   
   
   

   rhc app-create -a MyApp -t ruby​​-1.9 --no-git

   
   
   

   -a在OpenShift下设置应用程序名称 - 它可以与rails应用程序名称完全不同

   
   
   

   -t设置应用程序类型 - 我认为现在的红宝石1.9是他们支持的最高版本

   
   
   

   - no-git告诉不要创建git - 因为我们已经有一个

   / li>
   

8. 设置您的数据库

   
   
   
   
   

   • 为您的OpenShift应用程序安装适当的DB墨盒通过调用

     
     
     

     rhc cartridge add< DB cartridge type> -a<应用程序名称>

     
     
     

     例如：

     
     
     

     rhc cartridge添加mysql-5.1 -a MyApp

     
     
     

     它还支持MongoDB和PostgreSQL

     
     
     

     （见这里）

   
   

   • 将您的database.yml更改为与OpenShift数据库相关 - 现在，这非常容易，因为OpenShift将其大量配置作为环境变量，您可以简单地使用它你需要 - 例如：

   
   
   
   
   




9. 确保一切都在本地工作

   
   
   
   
   
   • 运行：'bundle install'
   
   
   • 运行：'rails s' - 看到一切正常
   
   



10. Git - 将OpenShift存储库添加为您的远程存储库之一，然后推送它

    
    
    
    
    
    • 确保您的所有工作都更新，提交并与您的GitHub同步 - 这可以节省很多麻烦。
    
    
    • 运行： rhc app-show< application name> - 这将显示您所有关于您的应用程序的信息 - 复制Git URL
    
    
    • 运行： git remote add openshift< OpenShift repo URL>
    
    

    • 通过合并取得OpenShift正在添加的任何内容

      
      
      

      运行： git merge openshift / master -s recursive -X our

    
    

    • 提交更改： git commit -am'添加OpenShift文件

    
    
    • 推到OpenShift： git push openshift
    
    

现在您的应用程序应该部署在OpenShift上

如何打开我部署的网站？

使用 rhc app-show< application name> 命令可以看到您的网站URL

通常是 http：//< application name> - < domain name> .rhcloud.com

将其更改为您自己的域名很容易

• 只需运行 rhc alias add< app name> ; <您的域>


• 然后在您的DNS管理 - 编辑CNAME'www'定义指向
  http ：//< application name> - < domain name> .rhcloud.com

如何连接到我的OpenShift机器？

再次使用 rhc app-show< application name> 您可以看到SSH地址
只需运行 ssh< SSH地址> 以连接

如何在部署后自动运行迁移和种子？

OpenShift中的一个好处是可以添加自定义操作（动作挂钩）在部署的不同阶段被触发

您可以在这里阅读更多关于

现在，我只会谈谈部署动作钩子

1. 在您的应用程序文件夹下，转到.openshift / action_hooks并创建一个名为 deploy under it


2. 使此文件可执行 - 运行： chmod + x deploy



3. 将一些代码加入

   
   
   

   例如：

   
   
   

   
   
   • 稍后将说明软链接 - 路由需要找到载波文件
   
   


4. 将文件添加到您的git - git add deploy 文件夹当然）


5. 提交您的更改并推送到openshift远程

如何集成Carrierwave，以便我可以上传文件并保存在OpenShift？

有两点

1. 文件将在哪里保存？ - 这很容易


2. 路由知道如何获取我上传的文件？

设置保存路径

将initializers\carrierwave.rb文件设置为

  CarrierWave.configure do | config | 
如果Rails.env.production？ 
 config.storage =：file 
 config.enable_processing = true 
 config.root = ENV ['OPENSHIFT_DATA_DIR'] 
 config.cache_dir = config.root +'uploads'
 end 
 end 
  

默认情况下离开上传者，意思是 storage：file

和

使用$ OPENSHIFT_DATA_DIR文件夹将确保我们能够写文件，它将留在那里

确保路由将找到文件：

花了我一段时间才想出这个伎俩（不是太多，只是几个小时）

Rails路由知道如何只关联文件夹这是在应用程序文件夹下 - soo，在OpenShift机器上，它会看起来对于$ {OPENSHIFT_REPO_DIR} \public文件夹下的上传文件文件夹（名称为 uploads ），这是我将部署中的软链接文件变得方便 - 它只是欺骗系统，并使其从不在应用程序文件夹下的文件夹中获取文件

---

我知道有很多关于这些问题的帖子，以及如何部署和所有内容，但是我只是希望对其进行一些订单。

当然，由于我没有记录每一步的方法，只是从我记得，如果我在某些细节上出错，请随时纠正我的意见，因为我写的内容可能会有错误和不准确之处。

最好的资料之一是OpenShift文档

我希望这些东西能帮助人们节省时间和钱

享受

I'm starting a new small venture, a POC if you would like, and I want to deploy my Rails application for free somewhere.I found that there is Heroku, are there another options?

解决方案

Yes there are

This is a very good post I found on the subject

http://blog.sudobits.com/2013/02/15/heroku-alternatives-for-deploying-rails-applications

I went over the options there one by one and, to my humble opinion, OpenShift is the best option for a small-medium website, at least for the beginning of developing and creating a POC\Prototype

Why is it better?

• It gives you what Heroku will give you
• It give you local (persistant) storage - So you don't need to pay for S3 on Amazon or equivalent - I guess that in some point you would like to do that (to use S3), but at least for the begining you don't need to put money on it
• It seems that the website is running faster
• I find it more flexible in terms of controlling what is happening on the machine

Are there any disadvantages?

• The only disadvantage I could find on Openshift is that it seems that the deployment takes much more time then on Heroku and there is considerable delay on the first time you address the website (But after the first time is working faster - Not related to browser caching if you think this is the issue)

It might be that the Gemfile section under this document https://www.openshift.com/blogs/converting-an-existing-rails-app-to-run-on-openshift can solve this issue...I will try it later

What are the steps I need to do in order to deploy my already existing application on Openshift?

In many places I found explanations about how to create and deploy new application, but it was a little bit hard to understand how to put my already existing application on OpenShift

This is the reason I want to explain that

Assumptions- Your application is git controlled already- Its path is /home/dev/MyApp- you are now under /home/dev

1. Create Openshift account on https://www.openshift.com
2. Use the command line tools, I found them much more informative
3. Go to https://www.openshift.com/get-started
4. Follow steps 1..3 in order to install and setup the command line tools
5. cd to your rails application folder /home/dev/MyApp
6. Create a new application domain - Run : rhc domain-create <domain name>

7. Create your application in OpenShift by running

   rhc app-create -a MyApp -t ruby-1.9 --no-git

   -a sets the application name under OpenShift - It can be something totally different from your rails application name

   -t sets the application type - I think that for now ruby 1.9 is their highest supported version

   --no-git tells not to create git - Because we already got one

8. Setup your DB

   • Install the appropriate DB cartridge for your OpenShift application by calling

     rhc cartridge add <DB cartridge type> -a <Application Name>

     For example :

     rhc cartridge add mysql-5.1 -a MyApp

     It also supports MongoDB and PostgreSQL

     (see here https://www.openshift.com/developers/technologies)

   • Change your database.yml to relate to the OpenShift database - Now, that is very easy since OpenShift got a lot of its configuration as environment variables and you can simply use it wherever you need - For example :

9. Make sure everything is working locally

   • Run : 'bundle install'
   • Run : 'rails s' - See that everything is OK

10. Git - Add the OpenShift repository as one of your remote repositories and push it

    • Make sure all your work is updated , commited and syncronized with your GitHub - This can save a lot of headach later
    • Run : rhc app-show <application name> - This will show you all the information about your application - Copy the Git URL
    • Run : git remote add openshift <OpenShift repo URL>

    • Take whatever OpenShift is adding by merging

      Run : git merge openshift/master -s recursive -X ours

    • Commit the changes : git commit -am 'adding OpenShift files

    • Push to OpenShift : git push openshift

That is all , now your application should be deployed on OpenShift

How do I open my deployed web site?

Using the rhc app-show <application name> command you can see your website url

It will usually be http://<application name>-<domain name>.rhcloud.com

It is quite easy to change it to your own domain

• Just run rhc alias add <app name> <your domain>
• Then in your DNS management - Edit the CNAME 'www' definition to point tohttp://<application name>-<domain name>.rhcloud.com

How do I connect to my OpenShift machine?

Again , using rhc app-show <application name> you can see the SSH addressSimply run ssh <SSH address> in order to connect

How do I run the migrate and seed automatically upon deployment?

One nice thing in OpenShift is the ability to add custom actions (action-hooks) that are being triggered in different stages of the deployment

You can read more about it here https://www.openshift.com/developers/deploying-and-building-applications

For now, I will only talk about the deploy action-hook

1. Under your application folder go to .openshift/action_hooks and create a file named deploy under it
2. Make this file executable - Run : chmod +x deploy

3. Put some code into it

   For example:

   • The soft link will be explained later - it is needed for the routing to find the Carrierwave uploaded files
4. Add the file to your git - git add deploy (from inside the folder of course)
5. Commit your changes and push to openshift remote

How can I integrate Carrierwave so I could upload files and save on OpenShift?

There are two points

1. Where will the files be saved ? - This is easy
2. Will the routing know how to fetch my uploaded files ?

Setting the saving path:

Set the initializers\carrierwave.rb file to be

CarrierWave.configure do |config|
  if Rails.env.production?
    config.storage = :file
    config.enable_processing = true
    config.root = ENV['OPENSHIFT_DATA_DIR']
    config.cache_dir = config.root + 'uploads'
  end
end

leave the uploaders as they are by default, meaning storage :file

and

The use of the $OPENSHIFT_DATA_DIR folder will make sure we will be able to write the files and that it will stay there

Making sure the routing will find the files:

It took me a while to come up with that trick (not too much, just a couple of hours)

Rails routing knows how to relate only the the folders that are under the application folder - soo, on OpenShift machine, it will look for the uploaded files folder (named uploads in our case) under the ${OPENSHIFT_REPO_DIR}\public folder , this is where the soft link I put in the deploy file is becoming handy - It simply cheats the system and making it to go and fetch those file from a folder which is not under the application folder

---

I know there are a lot of posts about those issues and how to deploy and everything, but I just wanted to put some order into it.

Of course there might be mistakes and inaccuracies in what I wrote since I didn't documented every step of the way but just from what I remember, feel free to correct me if I'm wrong in some details.

One of the best sourced is the OpenShift documentation

I hope those things will help people and save you time and money

Enjoy

这篇关于部署Ruby on Rails - Heroku有很好的选择吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！