Re: A few Delayed Job questions
I believe it's Delayed::Job.all , not DelayedJob -Nick On Tue, Jun 1, 2010 at 8:57 PM, empika edw...@nixonmcinnes.co.uk wrote: Hallo Does anyone know the answer to the following questions... Is it possible to get a list of currently waiting delayed jobs? Opening a heroku console and trying to find them give me an error: ds = DelayedJob.all LoadError: Expected /disk1/home/slugs/XYZ/mnt/vendor/plugins/ delayed_job/lib/delayed_job.rb to define DelayedJob Also, do delayed jobs get profiled on New Relic? I may need to start running quite a few soon, although im not sure how ill be able to tell that only running one job is not enough to handle all the users across my app. Thanks Edd -- 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.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: Autocomplete slow on Heroku
Are you using MySQL to develop locally instead of Postgres? MySQL considers
LIKE case insensitive, you need to use ILIKE on postgresql to get the same
behavior.
-Nick
On Tue, Jan 26, 2010 at 10:20 AM, Sunny Beach sunnybeach1...@gmail.comwrote:
I have narrowed down the problem to capitalization. If the query
string matches up (exactly) then all is well.
BAD:
http://content-tracker.heroku.com/program_names.js?q=inter
GOOD: (finds three International... programs)
http://content-tracker.heroku.com/program_names.js?q=Inter
I have not been able to figure out how to fix this.
You can see the full list of programs (only 20 currently):
http://content-tracker.heroku.com/program_names.js
Sunny
On Jan 25, 11:20 pm, Sunny Beach sunnybeach1...@gmail.com wrote:
I have a small app that has a single Jquery Autocomplete field. It
seems very slow and spotty (not returning all the results it should)
on Heroku. It does work but not very well.
Is this due to the differences in databases between here and Heroku?
The call for the autocomplete is:
ProgramName.find(:all, :conditions = ['name LIKE ?', %#{params[:q]}%])
Is it due to a query limit (I am the only person using it at the moment).
Any ideas?
Thanks,
Sunny
--
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.comheroku%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
--
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: Sass_on_heroku compiled css shows line number
Have you tried out http://github.com/pedro/hassle ? I think it should pass through the options properly. On Mon, Jan 11, 2010 at 12:40 PM, Karl threadh...@gmail.com wrote: Sorry Devyn, but the config is correct or there would be no sass compiled css generated at all. Config is not the issue. On Jan 11, 10:27 am, Devyn Cairns devyn.cai...@gmail.com wrote: Well, you can just put haml in .gems: # file .gems haml And then you just need to haml --rails myapp -- 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.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: password protected site
Rack has this baked in, the Sinatra docs have a good example of using it: http://www.sinatrarb.com/faq.html#auth On Mon, Dec 7, 2009 at 11:35 AM, Bradley bradleyrobert...@gmail.com wrote: Is it possible to password protect a site, through something like http auth? I want to set up testing and staging sites, but I don't want these to be public and I don't want to have these restrictions in the code of my app. -- 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.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: pushing branches to heroku
git push heroku v2:master From the git docs: The special refspec : (or +: to allow non-fast-forward updates) directs git to push matching branches: for every branch that exists on the local side, the remote side is updated if a branch of the same name already exists on the remote side. http://www.kernel.org/pub/software/scm/git/docs/git-push.html On Mon, Nov 30, 2009 at 10:38 PM, Kyle Bragger kyle.brag...@gmail.comwrote: What happens if I am working in branch (called v2 for instance) and want to do a 'git push 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.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: installing gems from gemcutter not as it should be
It's working for me... % gem fetch RedCloth -Vv 4.2.0 GET 200 OK: http://gemcutter.org/specs.4.8.gz Downloading gem RedCloth-4.2.0.gem GET 302 Moved Temporarily: http://gemcutter.org/gems/RedCloth-4.2.0.gem GET 200 OK: http://s3.amazonaws.com/gemcutter_production/gems/RedCloth-4.2.0.gem Downloaded RedCloth-4.2.0 Perhaps it was a temporary fluke? Does it work now? -Nick On Thu, Oct 29, 2009 at 9:55 AM, markdevilliers markdevilli...@gmail.comwrote: Hey Guys - not too sure if I should post this here but I keep getting the following type errors - Heroku receiving push - Installing gem right_aws 1.10.0 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed right_http_connection-1.2.4 Successfully installed right_aws-1.10.0 2 gems installed - Installing gem right_http_connection 1.2.4 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed right_http_connection-1.2.4 1 gem installed - Installing gem populator 0.2.5 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed populator-0.2.5 1 gem installed - Installing gem faker 0.3.1 from http://gemcutter.org, http://gems.rubyforge.org Successfully installed faker-0.3.1 1 gem installed - Installing gem RedCloth 4.2.0 from http://gemcutter.org, http://gems.rubyforge.org ERROR: http://gemcutter.org/ does not appear to be a repository ERROR: could not find gem RedCloth locally or in a repository error: hooks/pre-receive exited with error code 1 To me it looks like maybe more from the gemcutter side than the heroku side but it is stopping me from deploying as is. Annoyingly it did work earlier on in the day By the way is this the best way to contact you guys if we are having service problems? Thanks, Mark --~--~-~--~~~---~--~~ 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: ERROR: could not find gem chronic locally or in a repository
All of gems from gems.github.com are prefixed with a username, so that won't work. If you leave off the source it'll pick chronic up from gemcutter: http://gemcutter.org/gems/chronic -Nick On Wed, Oct 21, 2009 at 2:10 PM, Shpigford j...@joshpigford.com wrote: I'm trying to install the chronic gem with my app and keep getting ERROR: could not find gem chronic locally or in a repository when I try to deploy to heroku. I've got this in my .gems file: chronic --source http://gems.github.com; And during deploy it spits this out: Installing gem chronic from http://gems.github.com, http://gemcutter.org, http://gems.rubyforge.org ERROR: could not find gem chronic locally or in a repository Not sure what else to try. --~--~-~--~~~---~--~~ 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: installing gems from gemcutter not as it should be
Yes, we are. http://github.com/qrush/gemcutter/blob/master/app/metal/hostess.rb#L13-34 -Nick On Mon, Nov 2, 2009 at 1:17 PM, Keenan Brock kee...@thebrocks.net wrote: Just a thought. Are the requests to gemcutter using HTTP? Is the system using ETags / If-Mod-since? Seems there could be a way to use a forward proxy to gemcutter. It would help out: 1) less bandwidth for both gemcutter and heroku 2) faster image build times on heroku 3) less load on the gemcutter servers 4) maybe less load on the heroku servers since Another option would be to have a local repository of gems. I remember doing this with rpms/gentoo ports. It was a bit of a pain but as the number of machines increased, it really sped things up. (Especially when installing the software) --Keenan On Nov 2, 2009, at 11:51 AM, Neil Middleton wrote: I had this same problem last week - in the end, and on about the tenth push it finally managed to make it through which was a real pita. Something needs to be there to ensure deployments aren't killedwhatever that might be. /Neil On 2 Nov 2009, at 16:46, markdevilliers wrote: It did work for me a couple of hours later. It had also failed several times before I posted. I think the issue is consistency - random gems (not always redcloth) were failing to install with the error message - http:// gemcutter.org/ does not appear to be a repository - which in the example above doesn't make sense as it was a repository moments before. I'll probably accept that maybe gemcutter is a bit overloaded a certain times and timing out delivering the initial 302 but maybe on the heroku side there needs to be a try a few times on push as failing at random stages is a bit annoying. Anyway I've just pushed again and all is good again, Thanks for looking into it for me - Mark --~--~-~--~~~---~--~~ 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: Bulk data seeding
You should be able to use db:push/pull: http://docs.heroku.com/taps I'm frequently moving around the database for Gemcutter around my various machines and its production/staging apps, and there's over 100,000 rows now. Takes around a minute to pull, a little longer to push. -Nick On Mon, Oct 5, 2009 at 7:16 PM, dburkes dbur...@gmail.com wrote: I've got 42,000 rows of data that I need to seed into an existing table in a Heroku database. From our previous non-Heroku deployment, I have a rake task that does this in MySQL by spawning the mysql executable and using the LOAD DATA INFILE command. What's the suggested way to do large data seeds in a Heroku deployment? Thanks! Danny Burkes --~--~-~--~~~---~--~~ 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: Git
Did you create a heroku app with `heroku create` ? Also, you should be able to see the git remote url if you login to your account at http://heroku.comand click on the app name. Then you should just be able to do `git remote add heroku [git url]` and then push away. -Nick On Wed, Sep 9, 2009 at 9:32 AM, Nemrah harmenh...@gmail.com wrote: Hi i installed ruby m rubygems , git and the heroku gem. I was following all the steps described in the docs sections of Heroku when i walked into this error : fatal: 'heroku' does not appear to be a git repository fatal: The remote end hung up unexpectedly , i got it after typing the git push heroku master command. Whats i going wrong and what can i do to fix this ? Thanks , Nemrah --~--~-~--~~~---~--~~ 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: shows buffer error when run rake gems:install for missing gems
It looks like you've got config.gem calendar_date_select somewhere in one of your environment files: config/environment.rb, or config/environments/production.rb. If you no longer need that gem, I would delete that line from there. If you don't understand what's going on here with gem dependencies for your app, I would definitely read into it a little more: http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies -Nick On Tue, Sep 15, 2009 at 4:43 AM, sravi rordevolo...@gmail.com wrote: Hi all, Iam new to Heroku and git.I deplyoing ruby on rails code to heroku through git in windows XP.Iam following the article. http://wiki.devchix.com/index.php?title=Server_2003 all working fine but at the end when i run rake heroku rake db:migrate .It showing error like this. Missing these required gems: calendar_date_select You're running: ruby 1.8.6.287 at /usr/local/bin/ruby rubygems 1.3.5 at /home/slugs/55586_39407b1_f6bf/mnt/.gems, /usr/lib/ ruby/gems/1.8, /usr/local/lib/ruby/gems/1.8 Run `rake gems:install` to install the missing gems. so i tried to run rake gems:install in git bash it giving buffer error.and tried as gem install calender_date_select but it also not working. Actually that gem doesn't required for me now. so how i can i install or uninstall gem froom apllication in this stage of deployment.Please tell help.waiting for your reply. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Postgres Invalid Byte Sequence
Hey folks, I've been banging my head over this for the past few hours and have come up with not much. I'm getting this error: PGError: ERROR: invalid byte sequence for encoding UTF8: 0xf6726465 HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by client_encoding. : INSERT INTO versions (rubyforge_project, updated_at, platform, number, description, summary, indexed, authors, rubygem_id, built_at, created_at) VALUES(NULL, '2009-09-08 22:37:10.573001', E'mswin32', E'0.1.0', NULL, E'GUI for ''net send''', 't', E'Sascha D�rdelmann', 20501, '2005-01-11 08:00:00.00', '2009-09-08 22:37:10.573001') RETURNING id Now, it seems like it's trying to insert an author name with an umlaut in it, which seems like a valid character to me. This is coming from a RubyGem spec, so it looks like this in the YAML version: authors: - Sascha D\xF6rdelmann and like so as Ruby: s.authors = [Sascha D\366rdelmann] The latter is what I'm seeing when loading it manually via script/console. Is there some postgres setting I'm missing here, or am I just doing it wrong? Thanks! -Nick --~--~-~--~~~---~--~~ 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: s3-paperclip uploads hanging indefinitely
Alright, I think I've tracked down in my codebase where the problem is. Sorry for the red herring here, folks. Still though, it would be nice to see the logs. On Fri, Jul 31, 2009 at 12:02 AM, Chris Conley chris.m.con...@gmail.comwrote: Paperclip uploads have been working fine for me. On Thu, Jul 30, 2009 at 11:40 PM, Nick Quaranto n...@quaran.to wrote: Pedro, I'm seeing it consistently. Is there any way to look at the crashed logs? -Nick On Thu, Jul 30, 2009 at 9:25 PM, Trevor Turk trevort...@gmail.comwrote: On Jul 30, 7:48 pm, Pedro Belo pe...@heroku.com wrote: Hey guys, we're still taking a look at this, but having trouble to reproduce it. Nick, do you get a failwhale consistently when you run this command? Anyone else is seeing this problem consistently? Thanks for working on this, Pedro. I'm not seeing the problem very much (if at all) today. When it was happening, it was very consistent, though. Sorry, I know that's not much help! Hopefully, someone else on here is having a consistent problem that you might be able to work out. Thanks, - Trevor --~--~-~--~~~---~--~~ 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: s3-paperclip uploads hanging indefinitely
Alright, so looks like I've traced down the problem but I'm still not sure of how to resolve it. Part of my application deals with a pretty huge file, it's basically a giant list of all 23,000+ gems available on Gemcutter. Compressed, this is a little less than 2 megs (with Gem.deflate, which uses Zlib) and uncompressed, it comes down to ~14 megs if you write out the file. On my own machine this turned out to be slow, but usable...on Heroku it's causing an internal system error when deserializing it using Marshal.load. To recap, the process looks something like this when pushing a new gem: 1) Download zipped index from S3 2) Unzip 3) Deserialize (boom, internal server error) 4) Add new gem into the index 5) Serialize 6) Zip 7) Push back to s3 I'm seeing a few options here...one, to try out different serialization formats to see if that helps. Another is to stick it in Memcached, but my main problem with that is I can't lose that data...so perhaps I could back it up hourly to S3. I could even make a giant binary blob in Postgres, but I doubt that would be ideal. If you've got other suggestions on how to deal with a pretty massive file like this, I'd be glad to hear it. Thanks, -Nick On Fri, Jul 31, 2009 at 12:18 AM, Trevor Turk trevort...@gmail.com wrote: On Jul 30, 11:11 pm, Nick Quaranto n...@quaran.to wrote: Alright, I think I've tracked down in my codebase where the problem is. Sorry for the red herring here, folks. Still though, it would be nice to see the logs. Please do let us know if/when you figure it out! - Trevor --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Upgrade Rubygems to 1.3.3 or greater
Hey folks, I'm wondering if Rubygems could get upgraded on the Heroku systems to 1.3.3 or greater, the latest version (1.3.5) would be best. Gemcutter ( http://gemcutter.org ) depends on the latest version, and currently I'm getting around that by tossing the code in my lib directory and requiring in what I need to override it. However, something is definitely going wrong with that when trying to push to gemcutter (see the segfault?): == log/server_33403_23bb188_e4eb_54790.log == /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.2/lib/ action_controller/vendor/rack-1.0/rack.rb:17: warning: already initialized constant VERSION ./lib/rubygems.rb:193: warning: already initialized constant MUTEX ./lib/rubygems.rb:195: warning: already initialized constant RubyGemsPackageVersion ./lib/rubygems.rb:207: warning: already initialized constant WIN_PATTERNS ./lib/rubygems.rb:1078: warning: already initialized constant MARSHAL_SPEC_DIR ./lib/rubygems.rb:1083: warning: already initialized constant YAML_SPEC_DIR ./lib/rubygems/platform.rb:171: warning: already initialized constant RUBY ./lib/rubygems/platform.rb:177: warning: already initialized constant CURRENT ./lib/rubygems/source_index.rb:587: warning: already initialized constant Cache ./lib/rubygems/version.rb:246: warning: already initialized constant Requirement ./lib/rubygems/version.rb:36: [BUG] Segmentation fault ruby 1.8.6 (2008-08-11) [x86_64-linux] Thin web server (v1.0.1 codename ?) Maximum connections set to 1024 Listening on 0.0.0.0:54790, CTRL+C to stop /usr/local/bin/thin_launcher: line 5: 19862 Aborted thin -p $1 -e $RACK_ENV -R /home/heroku_rack/heroku.ru start $2 21 The strange part is that pushing was working a few days ago, this seems to be a relatively recent issue. I think upgrading to the latest recommended version of Rubygems is a good decision overall and I'd like to make sure that this isn't the cause for this bug. 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: s3-paperclip uploads hanging indefinitely
I'm seeing the exact same behavior when pushing gems to Gemcutter. The log just totally disappears once the failwhale comes up. % heroku logs == log/production.log == # Logfile created on Wed Jul 29 14:36:17 -0700 2009 == log/server_33403_5ae9691_e4eb_30955.log == /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.2/lib/action_controller/vendor/rack-1.0/rack.rb:17: warning: already initialized constant VERSION % gem push pkg/gemcutter-0.0.6.gem Enter your Gemcutter credentials. Don't have an account yet? Create one at http://gemcutter.org/sign_up Email: n...@quaran.to Password: Signed in. Your api key has been stored in ~/.gemrc Pushing gem to Gemcutter... !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html head meta http-equiv=Content-Type content=text/html; charset=utf-8 / titleHeroku Fail Whale/title /head body div style=margin: 2em 5em h1Heroku Error/h1 img src=http://heroku.com/images/pages/japan.gif; style=float: left; margin-right: 1em / h3Oops, we seem to have a glitch in our system./h3 pWe've been notified; you might try reloading the page in a little while./p /div /body /html % heroku logs Nothing is returned for the logs after this. Is there any way the log file from the instance can be tracked down and seen again? On Wed, Jul 29, 2009 at 5:06 PM, Trevor Turk trevort...@gmail.com wrote: On Jul 29, 4:02 pm, Pius Uzamere pius.uzam...@gmail.com wrote: One of the frustrating aspects to this (at least in my case) is that it seems to be failing silently; there's nothing in the logs, the app just churns. If it helps, I am using this base app: http://github.com/dancroak/heroku_suspenders/tree/masterto do the uploads. Yeah, this was the same with me. Things seem to be working properly now, but I'm concerned that the issue might reappear if the cause was unknown... Can you guys test things out again and post your results? - Trevor --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
DNS Confusion
Sorry if this was double posted, I didn't see it showing up on Google Groups. Hey folks, I'm really confused with trying to set up a custom domain for Heroku. I don't understand DNS too well, so any help would be appreciated. Currently here's the setup I have: I'm using GoDaddy and Slicehost, and I want to move hosting over to Heroku while still using Slicehost's DNS management. GoDaddy knows the nameservers are ns1, ns2, and ns3.slicehost.net. On slicehost's DNS management I have the following records: name | data | record type gemcutter.org. proxy.heroku.com CNAME gemcutter.org. ASPMX3.GOOGLEMAIL.COM. MX gemcutter.org. ASPMX4.GOOGLEMAIL.COM. MX gemcutter.org. ASPMX5.GOOGLEMAIL.COM. MX gemcutter.org. ASPMX.L.GOOGLE.COM. MX gemcutter.org. ASPMX2.GOOGLEMAIL.COM. MX gemcutter.org. ALT2.ASPMX.L.GOOGLE.COM. MX gemcutter.org. ALT1.ASPMX.L.GOOGLE.COM. MX gemcutter.org. ns3.slicehost.net. NS gemcutter.org. ns2.slicehost.net. NS gemcutter.org. ns1.slicehost.net. NS Do I even need the NS records anymore? Should GoDaddy be told that my nameservers are still on slicehost? They can forward domains as well, but Im not sure if that's the same. Also, I'd like to have google apps for this domain as well. Is the CNAME for heroku set up correctly? Any sort of transition information would be appreciated, I'm sure that I'm not the only person that's been really confused with trying to move hosting over. Thanks! -Nick --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
