Disqus - Latest Comments for rwdaigle

Re: Exposing a Javascript API in a Web Page with Browserify

Ryan Daigle — Mon, 15 Jun 2015 13:16:10 -0000

onesixtieth I think your best bet is to do your own sub-namespacing so there's a single top-level entity that contains MyBookStore and MyLibrary?

var lib = new MyLibrary();

// Now use lib.BookStore and lib.Library ?

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Wed, 10 Jun 2015 08:03:14 -0000

Hi @eggie5, I believe you mean the first picture? If so, that's just showing you how your records look like after you add your domain to Cloudflare - it's their default config. You're correct, though, in that after you go through the steps mentioned here, you won't have an A record.

Sorry if that initial pic was a little misleading!

Re: Time-Series Database Design with InfluxDB

Ryan Daigle — Tue, 19 May 2015 16:08:05 -0000

Hi Fred,

It's been awhile since I've thought about this (since Influx is just humming away so far), but I think I can help.

First, regarding time-scoping queries, I think the original issue I had was caused by a bug that has since been fixed. However, being aware of the size of the dataset being queried is never a bad thing. I'd recommend the following:

* Keeping a per-customer series containing all their transaction values, e.g., `customer-123.transaction_values`, `customer-abc.transaction_values` etc...
* Create a continuous query that automatically populates a per-customer lifetime value series:
`select sum(value) as value from /^customer-*.*/ into :series_name.lifetime`. This will create series called `customer-123.transaction_values.lifetime` etc... containing pre-summed values.

That's one way to think about it. I can easily think of a few others too. Let me know what you come up with!

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Thu, 11 Dec 2014 13:40:32 -0000

Hi @arronjeffery,

If you mean: Is there a way to create a single wildcard CNAME DNS record that points to multiple Heroku apps, I believe the answer is "no". However, I suspect there might be some room for an alternative solution. Can you explain what you're trying to do and, specifically, how you're hoping to map a request URL to a specific Heroku app?

Re: Time-Series Database Design with InfluxDB

Ryan Daigle — Wed, 03 Dec 2014 09:58:22 -0000

Hi Yngui,

In this example the continuous query is not extracting "the abc123 part of the series names to become part of the datapoints". That is your responsibility when you populate the series. What's happening is almost the inverse of that.

What I'm suggesting is to create a series with data that includes an "account" field (or some other field you want to query on). This series you can operate against to do summary calculations (across all accounts). Then, use continuous queries to create series specific to each account.

When you define a continuous query you can "pull up" a field value to be part of the new series name, so you can essentially create a series named for each account (account-abc123.gateway.sample) without having to do any creation or population yourself. So start with a series that has many filterable fields, and use continuous queries to automatically generate single-purpose series from each field.

I hope that helps. The Influx docs have a section on continuous queries in case their description is more intuitive for you than mine: http://influxdb.com/docs/v0....

Re: Time-Series Database Design with InfluxDB

Ryan Daigle — Fri, 31 Oct 2014 10:25:22 -0000

Usually a time-series db will store the events that occur in your system. It is not intended as a general data store. So, yes, usually there's a canonical "this is our data right now" conventional database that houses what you call static data alongside your Influx db which stores more temporal data.

Hope that helps!

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Tue, 07 Oct 2014 10:00:39 -0000

Yes, you will now need to discard the existing A record when you add the root domain CNAME.

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Tue, 07 Oct 2014 09:58:58 -0000

Yes it is. Just add a CNAME record mapped as rootdomain.com -> yourapp.herokuapp.com. I just recently updated the article to reflect this.

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Tue, 07 Oct 2014 09:57:24 -0000

@rassom We just updated the article yesterday. Let me know if it helps!

Re: Time-Series Database Design with InfluxDB

Ryan Daigle — Thu, 14 Aug 2014 11:33:55 -0000

I'm not sure what you mean here by "table names"?

Re: Time-Series Database Design with InfluxDB

Ryan Daigle — Thu, 14 Aug 2014 11:32:56 -0000

That's right, Kimo. It's a great way to automate the segmentation of your data into special-purpose series while still retaining the usefulness of the general series for higher level queries.

Re: A frontend UI for the Spreedly Core API

Ryan Daigle — Fri, 25 Jul 2014 10:35:44 -0000

This is great work, Dan.

Just a note that an "official" Spreedly Dashboard is in development and available for beta testers.

However, we're happy to see an ecosystem of tools around the Spreedly API and welcome alternatives!

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Thu, 15 May 2014 10:20:57 -0000

Yes! This was confirmed by Cloudflare - I just need to update the article...

Re: The New Gist: What It Is and What It Could Be

Ryan Daigle — Thu, 27 Mar 2014 11:38:22 -0000

Hey Dennis,

Haven't sent it to them directly, but know they were aware of it when I posted it.

Re: Using `pg:transfer` to Migrate Postgres Databases - Higher Order Heroku

Ryan Daigle — Thu, 19 Sep 2013 15:08:51 -0000

pg:transfer currently operates on whole databases only. To operate at a more granular level you're free to drop down to the raw Postgres tools like pg_dump (http://www.postgresql.org/d... and pg_restore (http://www.postgresql.org/d....

Re: Introducing Heroku Fork

Ryan Daigle — Mon, 08 Jul 2013 12:56:42 -0000

Thanks for the feedback, @Aldric Giacomoni. Tracking here: https://github.com/heroku/h...

Re: Introducing Heroku Fork

Ryan Daigle — Sat, 06 Jul 2013 20:46:20 -0000

Hi @srohde, app forking does not make any modifications to the source tree. The best way is to manage this process yourself by creating a new branch in Git and pushing this branch to the new app fork.

Re: Introducing Heroku Fork

Ryan Daigle — Tue, 02 Jul 2013 20:05:59 -0000

Hi @Stephen Corwin, I suspect you're not running the Heroku Toolbelt (https://toolbelt.heroku.com/) and, thus, don't have the latest CLI version. Try the instructions here to get the latest and greatest: https://devcenter.heroku.co...

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Fri, 28 Jun 2013 10:28:47 -0000

Hey @Chris, I'm not aware of any such integration plans so can't comment.

Re: Introducing Heroku Fork

Ryan Daigle — Fri, 28 Jun 2013 09:41:11 -0000

Hi @acjohnson55,

I'm not quite sure what you mean by "external service settings"? If you mean your add-on resource URLs and config vars - all add-on plans are re-provisioned which automatically creates new versions of these and avoids collisions with production values.

The only caveat is if you've manually added a pointer to an external resources using `$ heroku config:set`. In this case the value will be copied over verbatim since it's not associated with an add-on.

Re: Introducing Heroku Fork

Ryan Daigle — Thu, 27 Jun 2013 15:18:49 -0000

Hi JangoSteve,

This is a known, but unjustified, omission: https://github.com/heroku/h...

If you're interested in contributing, please feel free to submit a pull request to the CLI. Otherwise, we'll look at making incremental improvements as we gather more use-cases for the utility.

Thank you for this feedback!

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Wed, 05 Jun 2013 12:31:03 -0000

Hey Aaron. See the other comments in @Desinle 's thread. It's just a requirement of CloudFlare's setup. In reality, it doesn't get used to resolve any requests, but must be in the configuration.

Re: The New Gist: What It Is and What It Could Be

Ryan Daigle — Thu, 25 Apr 2013 09:40:40 -0000

Sure. Let me know if it's missing anything for you.

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Sun, 03 Mar 2013 19:36:47 -0000

I'm not sure if you mis-typed, but the purpose here is to redirect the root domain to the `www` subdomain, not the other way around. Your domain is doing this correctly:

$ curl -I xgd.in
HTTP/1.1 301 Moved Permanently
Server: cloudflare-nginx
Location: http://www.xgd.in/

It looks like everything is working as it should?

Re: Configuring CloudFlare DNS for a Heroku App - Higher Order Heroku

Ryan Daigle — Fri, 01 Mar 2013 14:25:44 -0000

Yes, the A-record is required.
It looks like you're setup ok now - did you change anything to get it working?