Re: Trace Application Error
Hi joshmckin, thank you very much for the support. I have tried to replicate the problem locally but I have found no error yet. I'm thinking a way to save the log realtime so I can parse it searching for the problem; the "advance" logging addon is out of my budget. On 20 Lug, 15:58, joshmckin wrote: > I've had a similar issue, since the application is crashing any system > built into the application for logging is crashing with it. New relic > can sometimes catch it but not always. Your best bet is build an > environment locally similar to Heroku (Nginx/Thin) and see if you can > replicate the error. For us it turned out Mysql2 gem was throwing > exceptions that would kill EventMachine and therefore kill Thin. Since > Thin was giving up its ghost, the logger would not record the > exception, once we were able to patch Mysql2 we were able to get to > the root exception. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Trace Application Error
Hi, some users are informing me that my application sometimes pop up an Application Error: -- Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details. -- I'm using Exception Notifier to log rails errors but it cannot log these errors because they are at heroku level. I'm unable to check the log because time has passed and it is not longer available. What can I do to log, be notified *instantly* and debug these errors? Thanks! -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Suggestion for Heroku - different error message when issue deriving from AWS
Yes, quite *sad*. In this cases the only solution is to have a backup hosting/server and do a DNS change. I "solved" this way. On 21 Apr, 21:19, chris wrote: > We created a custom error page and are seeing the heroku generic instead of > our prettiness. Sad... -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
API: error calling heroku.add_domain
Hi,
i'm hitting this error using the Heroku API:
>> heroku = Heroku::Client.new(ENV['HEROKU_USER'], ENV['HEROKU_PASSWORD'])
>> heroku.add_domain('myapp', 'test.com')
TypeError: can't convert RestClient::Payload::Base into String
/disk1/home/slugs/../mnt/vendor/rails/activesupport/lib/
active_support/core_ext/string/output_safety.rb:34:in
`concat_without_safety'
/disk1/home/slugs/../mnt/vendor/rails/activesupport/lib/
active_support/core_ext/string/output_safety.rb:34:in `<<'
/usr/ruby1.8.7/lib/ruby/1.8/openssl/buffering.rb:170:in `do_write'
/usr/ruby1.8.7/lib/ruby/1.8/openssl/buffering.rb:192:in `write'
The same error happens in local and using the Heroku console too.
Any tip please?
Regards,
Daniele
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: Heroku on serious applications and lack of support
Same thoughts here. The support request is not as fast as other providers I use. I didn't have critical issue (except for a problem to a primary key of the database, not set correctly during a push, that I solved myself) but I'm a little scared about the fact to stay offline with a slow support response. And yes, I'm a paying customer. On Sep 16, 10:22 pm, Abel Tamayo wrote: > Yeah, it can be frustrating some times. I have hope that they will improve > in this particular aspect soon though, so I'll stay true to Heroku. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Queue limit?
Thank you very much Jacob. On Sep 16, 7:05 pm, Jacob Vorreuter wrote: > The backlog too deep response is served once a request spends 15 seconds > queued up waiting for a backend. Once the wait queue reaches a length of 50 > requests, backlog too deep responses are served immediately. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom error pages, we *really* need them
A separate branch or a dedicated folder are not a solutions. When a system wide problem occurs (as 2 days ago) the dyno grid and probably the routing mesh too are broken, so all the "logic" part of the system is unavailable. Heroku can only serve a generic page. Perhaps it can personalize it with the request headers (es. domain name) but no more. So an iframe or an ajax setup is the only way. Different address for the message 'backlogged to deep" that could be personalized using a specific folder/file. But we have to point out when it pop up: during the system's problem phase I get a lot of these messages while the git repo was not probably accessible. So I will prefer an iframe/ajax solution in this case too. Daniele On Sep 15, 7:19 pm, Mike Abner wrote: > Why have a separate branch? Heroku can just tell us where to put them > in the folder hierarchy and they'll grab them from there. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Queue limit?
The queue is a numeric value you can see in the HTTP_X_HEROKU_QUEUE_DEPTH header. Of course it depends on the number of requests.. but I need to know the max length after which we get the error page. On Sep 15, 9:18 pm, Teng Siong Ong wrote: > it depends on how long your processing time for each request. usually, it is > about 5 requests per second. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Queue limit?
As subject, what is the limit above which appears the error "backlog too deep"? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Custom error pages, we *really* need them
Hi, as you can see from the status page in the past 2 days Heroku had a lot of problems that resulted in "Timeout connection" and "Backlog Too Deep" error pages. This two pages have a message specifically addressed to the administrator that is not acceptable in a production site. We need to have personalized pages. Same logic about the Heroku Ouchie Page of course! If this is not possible immediately a quick hack could be to have a really generic "white-label" page (multilingual would be appreciated) and put all the system message in an html comment. We are tech guys, right? Is not a problem to look at the source to find out what is happening. This seems clever that show a ugly error message to everyone. Finally as I already suggested in another discussion: A simple solution for more personalization without the need to access any preferences could be to have a full page iframe inside the heroku's error page pointing to http://error./.html The admin has to create a third/fourth level domain, point it to a different server and create the personalized pages. So every application can have an error page/backup application to handle the down. A js can check for the domain existence and switch to a plain txt message if it is not set. I'd love to get feedback on these ideas by Heroku guys. Thank you. Daniele -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom Error Pages
+1 for the unbranded page A simple solution for more personalization without the need to access any preferences could be to have a full page iframe inside the heroku's error page pointing to http://error.. So every application can have an error page/backup application to handle the down. A js can check for the domain existence and switch to a plain txt message if it is not set. On 5 Ago, 22:46, James Miller wrote: > That said, I agree there's no reason for there to be Heroku branding > in there. Just a simple, unbranded page for this status would be a > great start. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Varnish cache purging
sob... :) Thank you for the reply. On 23 Mag, 02:16, Oren Teich wrote: > That's wrong. I'll fix the docs. The only way to flush varnish right > now is to do a fresh git push. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Varnish cache purging
Hi, in the Heroku docs (http://docs.heroku.com/http-caching) I read: "Pressing shift-reload in the browser will cue the browser AND (my capitalization) Varnish to regenerate the page, regardless of the cache state." Instead in my experience Varnish does not regenerate the page. Is a bug? Any experience about that? Regards, Daniele -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: European data center?
+1 for EU datacenter :) On 24 Mar, 02:38, Morten Bagai wrote: > Thank for the comments. We continue to see strong interest in the Heroku > platform from European users, -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: pull/push in one step?
+1 Really nice feature! On 15 Mar, 18:57, Mike Doel wrote: > I imagine we're not alone in having both a staging and production environment > up on heroku. We frequently use heroku db:pull to grab the production > database and will occasionally put it up to our staging environment with > heroku db:push. > > Is it possible to do this in one step? Something like: > > heroku db:copy app1 app2 > > Ideally, this would happen without having to download locally and uploading > as separate steps (i.e. direct server-to-server transfer). -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Best way to add a huge dataset?
On 15 Mar, 01:13, Mike wrote: > That's a really good idea on having a controller take the upload into > temp. Is there a size limit on the temp directory? I don't know, sorry. > Or a time limit on > how long a dyno can be locked to a single upload before being > restarted? "Request Length: 30 seconds - Hard" (http://legal.heroku.com/aup) A bit low timeout for a middle-size upload... -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Best way to add a huge dataset?
This is an hard step and depend by the size of default dataset (?). Just an idea (I've not tested it): * Create a controller for the update with an upload field. * Upload a DB with the basic dataset only. The file will update in the /temp dir. * Find out you postgres config reading the config/database.yml * Execute (within the controller or by console) `psql ...` to import tables. Two ways: ** Realtime overwriting (perhaps you have to put the app in maintenance mode) ** Import with a different name, then delete the originals table and rename the new ones I don't know if Heroku folks are happy about this "a bit system level" procedure :P On 13 Mar, 01:46, Mike wrote: > Those are really good ideas. Would there be any way you can think of > to push data back up to the server? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Best way to add a huge dataset?
For the import part if it has not to be "atomic" you could create another app and use it to feed via a web service the data on the production database while the main app is live. To download only the main dataset create a boundle, animate it on a new application, delete the huge data with a migration or with a sql query in the console and the pull the database locally. By the way I'm investigating about how to work with big db too. Coming from a standard server world I love Heroku but some steps could be a bit less flexible. Nothing is perfect :) On 12 Mar, 07:29, Mike wrote: > I'm going to be adding a number of discrete, but enormous (maybe many > gigs each), datasets to my Heroku app's database. In many ways, I'm > in a similar situation faced by Tobin in another current post, but > with a different > question:http://groups.google.com/group/heroku/browse_thread/thread/141c3ef84b... > > Right now I still haven't merged the datasets into my database yet. > What's the best way for me to approach this? > > The lack of ability to push individual tables with taps suggests to me > I'm going to want to do this probably as a one shot deal, rather than > doing each dataset sequentially and testing that one before proceeding > to the next. I'm thinking about doing a db:pull to get the current > state of my database, and then shutting down my application in > maintenance mode, running a local merge of the datasets (maybe taking > days I'm guessing just to process the enormous things), doing some > exhaustive local testing on the result, and then doing a push back to > Heroku (maybe taking days again), before reactivating my app. Because > of their massive size, it seems like after I've done one, doing any > further db:pulls is going to be basically impossible. Just the idea > of possibly having made a mistake in merging the datasets that I don't > catch until after it's been pushed to the site gives me the shivers. > Overall, I wonder if there could be a better way that I'm overlooking. > > One possible alternative I thought of is would it be possible to do > something involving creating a local bundle from my database using > YamlDB? But then I'm not sure how to get the bundle back onto the > server and then to restore from it? The documentation on Heroku > doesn't seem to really talk about that possibility. > > Also, in my case this data is integral to the application, so I'm not > going to be able to split it up into a separate Heroku application > like in Tobin's case. Is there going to be any practical way for me > to be pulling just the non-dataset data from the server in order to > use on a development machine? > > Does anyone have any ideas on how they would approach this problem? > If so, I'd be filled with gratitude. > > Mike -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Maximum RAM per dyno?
Hi Carl, no problem :) As I wrote in another post I need to use (read & write) a small amount of data (about 200Kb) in a before_filter to. I need to operate *fast* and the DB is not a viable solution (the I need to pack it as plugin so I prefer to don't have any DB dependencies). Filesystem... is not supported on Heroku :P So locally I tested a global var and it did its work. Yes I know it is not a best practice. Any other ideas? Thank you for your time. On 10 Mar, 17:25, Carl Fyffe wrote: > Daniele, > > My apologies for coming across rude, it was not my intention, which > was why I apologized up front. As Chris said, there are better ways to > skin the global variable cat. Also, in most Ruby docs it says use them > sparingly: > > http://www.rubyist.net/~slagell/ruby/globalvars.html > > Which to most people means, avoid at all costs. You can put them in > the db. If they are constant and never change, you can put them in > config. If they are client specific, put them in a cookie and store > them in the browser (as long as they aren't huge). If they are huge, > then the database is your best bet because you don't want to clutter > your memory with it. If the database is to slow, then put it on the > file system. > > But whatever you do, please avoid using global variables. I have > googled for the article that explains why, but I can't find it. All I > could find was a repeat of the "use sparingly". > > As I said earlier, benchmark the easiest solution first. It might just > meet your needs. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Maximum RAM per dyno?
Thanks Chris, the memcached solution is right but: - it is in private beta (by the way I will send a mail to join the beta) - i don't know how much it will cost by I suppose that it will be too much (form me) to just handle some Kb What's I'm doing is a micro firewall that act as a filter before every request. So what I need it to keep a moderate size array in memory, read and write it *quickly*. Any suggestion are welcome. On 10 Mar, 16:38, Chris wrote: > Daniele, > If you really need a global variable to be accessible across servers > then memcached works good as long as it doesn't matter if that global > variable gets expired. You need to store the variable persistent in a > database. Pull it from memcached if it's there, if not then hit the > database. (Alternatively, depending on the variable, just re-create > it if it's expired and doesn't need to be persisted somewhere.) -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Maximum RAM per dyno?
Yes Carl, you tone is quite rude. And perhaps you reply to the wrong person. By the way I need the global variable for other uses, caching is not a problem for me. On 10 Mar, 15:51, Carl Fyffe wrote: > These kinds of questions crack me up. I am going to try to adress this > without sounding rude, but if I do happen to come across as rude and I > apologize for that up front. _cut -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Dynos & Queue Depth
Any news about that? On 9 Mar, 09:18, Daniele wrote: > Yes I know that. > But with on a single dyno app and 10 concurrent users I should always > have a queue of 9. Right? > I used a 1 sec dummy action to eliminate eventual ab delays that will > empty the queue faster. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Maximum RAM per dyno?
So a global variable $xx is not shared in the cloud?! On 10 Mar, 06:49, Oren Teich wrote: > I don't have a good answer for your question, but note there is no guarantee > that your requests will be served from the same physical machine - we'll > move the dyno around as demanded by the cloud. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Dynos & Queue Depth
Yes I know that. But with on a single dyno app and 10 concurrent users I should always have a queue of 9. Right? I used a 1 sec dummy action to eliminate eventual ab delays that will empty the queue faster. On 9 Mar, 00:49, Oren Teich wrote: > the queue is the list of what is waiting. > Requests coming in - requests getting served == queue. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Dynos & Queue Depth
Hi,
I wrote a simple test app to test the queue with a dummy 1 sec action.
The app has 1 syno active.
The controller:
class VisitmeController < ApplicationController
def test
sleep 1
render :text => "#{Time.now} - Queue:
#{request.headers["HTTP_X_HEROKU_QUEUE_DEPTH"]}"
end
end
So I lunch ab against it:
ab -c 10 -t 60 http://myapp.heroku.com/visitme/test
With a concurrency of 10 I should get a queue of 10, right?
Instead, while response times are correctly about 10 secs, the queue
is always at 5 or lower value. How can that be possibile?
Regards,
Daniele
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: Dynos pricing
Thank you Oren On 8 Mar, 19:34, Oren Teich wrote: > it's based on what you have set. Set dynos to 2 for an hour, and you'll pay > $0.05. Set it to 2 for 30 minutes, and you'll pay $0.025. We don't > currently auto-scale. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Dynos pricing
Hi all, from docs I read "subsequent dynos cost $0.05 per hour, prorated to the second". So I will pay dynos for effective seconds usage? Thank you in advance. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Connecting to the database from outside?
Of course I mean locked-in in a soft way :P Perhaps the wrong term, sorry for my bad english I'm used to think in the old server way, so for example I was unable to grasp how to implement an hight availability setup with a secondary server. But thinking about that the remote connection should not be stil enough. Perhaps ActiveResource can help me to replicate the data... On 5 Mar, 17:00, Carl Fyffe wrote: > Locked-In means no exit. If you want to take your data and leave, > Heroku provides db:pull to extract all of your data. If you want > access to the data as a service, Rails offers ActiveResource as > someone stated earlier. Heroku is probably the least locked-in > solution on the market today. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Connecting to the database from outside?
Hi Oren, thank you for the "official" reply :) RDS is not a solution because I only need to import some data. Then I love Postgres :) By the way I'm a little scared about been locked-in in the future too. I think that a way to connect from the outside (with an IP firewall policy too) could be a nice addon. On 4 Mar, 23:55, Oren Teich wrote: > It is not possible to connect to your heroku provided database from outside > your heroku application. > Amazon RDS may offer something for you. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Connecting to the database from outside?
Thanks Carl but this is not a viable solution because I have to push data while the app is running. I cannot stop it to backup - modify - restore On 4 Mar, 21:32, Carl Fyffe wrote: > Not sure if this meets your needs or not: > http://blog.heroku.com/archives/2009/3/18/push_and_pull_databases_to_... -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Connecting to the database from outside?
Hi Roy, you are right, I can modify my task to use ActiveResource. But it could be perhaps a quite long work... and I'm lazy :P On 4 Mar, 21:35, Roy Pardee wrote: > Hmmm--well I'd have a look at ActiveResource then. My understanding is that > it gives a local, scriptable interface (one that's very ActiveRecord-esque) > on remote rails apps via REST webservice type calls. I think the theory is > that you get a remote-accessible automation interface on your rails app for > the price of abiding by the various RESTful conventions that rails likes so > much. But someone should check me on that--I don't have any direct > experience w/it myself. > > Anyhoo--if that's not too far wrong, and assuming the overhead of the > underlying HTTP calls isn't too horrible to endure, I'm thinking you could > make DBI connections to your local mssql db, read stuff into memory, and > then push the data to your remote app via the ActiveResource objects. > > Cheers, > > -Roy > > > > > > On Thu, Mar 4, 2010 at 12:25 PM, Daniele wrote: > > Hi Roy, > > actually I have a rake task in my RoR app that connect to a remote > > MSSQL database and import data. This task use dbi with a quite complex > > system configuration. > > Because I cannot use it on Heroku it could be nice to setup the Heroku > > database as remote one on a second installation so I can use the > > migration task to push the data. > > > On 4 Mar, 21:12, Roy Pardee wrote: > > > Is it a rails app? If so, maybe a ruby script using the ActiveResource > > > library would work for you? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en. > > -- > Roy Pardeehttp://facebook.com/rpardee -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Connecting to the database from outside?
Hi Roy, actually I have a rake task in my RoR app that connect to a remote MSSQL database and import data. This task use dbi with a quite complex system configuration. Because I cannot use it on Heroku it could be nice to setup the Heroku database as remote one on a second installation so I can use the migration task to push the data. On 4 Mar, 21:12, Roy Pardee wrote: > Is it a rails app? If so, maybe a ruby script using the ActiveResource > library would work for you? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Connecting to the database from outside?
Hi, I have to connect to the Heroku database from a remote location, is it possibile? Regards, Daniele -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
