README.rdoc in alexrabarts-big_sitemap-0.3.0 vs README.rdoc in alexrabarts-big_sitemap-0.3.1
- old
+ new
@@ -24,11 +24,11 @@
1. public/sitemaps/sitemap_index.xml.gz
2. public/sitemaps/sitemap_products.xml.gz
3. public/sitemaps/sitemap_posts.xml.gz
-If your sitemaps grow beyond 50,000 URLs (this limit can be overridden with the <code>:max_per_sitemap</code> option), the sitemap files will be partitioned into multiple files (<code>sitemap_products_1.xml.gz</code>, <code>sitemap_products_2.xml.gz</code>, …).
+If your sitemaps grow beyond 50,000 URLs (this limit can be overridden with the <code>:max_per_sitemap</code> option), the sitemap files will be partitioned into multiple files (<code>sitemap_products_1.xml.gz</code>, <code>sitemap_products_2.xml.gz</code>, ...).
If you're using Rails then the URLs for each database record are generated with the <code>polymorphic_url</code> helper. That means that the URL for a record will be exactly what you would expect: generated with respect to the routing setup of your app. In other contexts where this helper isn't available, the URLs are generated in the form:
:base_url/:path/:to_param
@@ -42,20 +42,20 @@
== Advanced
=== Options
- * <code>:url_options</code> -- hash with <code>:host</code>, optionally <code>:port</code> and <code>:protocol</code>
- * <code>:base_url</code> -- string alternative to <code>:url_options</code>, e.g. "https://example.com:8080/"
- * <code>:document_root</code> -- string defaults to <code>Rails.root</code> or <code>Merb.root</code> if available
- * <code>:path</code> -- string defaults to 'sitemaps', which places sitemap files under the <code>/sitemaps</code> directory
- * <code>:max_per_sitemap</code> -- <code>50000</code>, which is the limit dictated by Google but can be less
- * <code>:batch_size</code> -- <code>1001</code> (not <code>1000</code> due to a bug in DataMapper)
- * <code>:gzip</code> -- <code>true</code>
- * <code>:ping_google</code> -- <code>true</code>
- * <code>:ping_yahoo</code> -- <code>false</code>, needs <code>:yahoo_app_id</code>
- * <code>:ping_msn</code> -- <code>false</code>
- * <code>:pink_ask</code> -- <code>false</code>
+* <code>:url_options</code> -- hash with <code>:host</code>, optionally <code>:port</code> and <code>:protocol</code>
+* <code>:base_url</code> -- string alternative to <code>:url_options</code>, e.g. "https://example.com:8080/"
+* <code>:document_root</code> -- string defaults to <code>Rails.root</code> or <code>Merb.root</code> if available
+* <code>:path</code> -- string defaults to 'sitemaps', which places sitemap files under the <code>/sitemaps</code> directory
+* <code>:max_per_sitemap</code> -- <code>50000</code>, which is the limit dictated by Google but can be less
+* <code>:batch_size</code> -- <code>1001</code> (not <code>1000</code> due to a bug in DataMapper)
+* <code>:gzip</code> -- <code>true</code>
+* <code>:ping_google</code> -- <code>true</code>
+* <code>:ping_yahoo</code> -- <code>false</code>, needs <code>:yahoo_app_id</code>
+* <code>:ping_msn</code> -- <code>false</code>
+* <code>:pink_ask</code> -- <code>false</code>
=== Chaining
You can chain methods together. You could even get away with as little code as: