Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices" rel="nofollow noreferrer">Gem Packaging: Best Practices</a> gives a lot of advice, some of which include</p> <ul> <li><p>Don't pollute the global load path. Ideally, only have <code>foo.rb</code> in your <code>lib</code> directory, and put all your other files in <code>lib/foo</code>.</p></li> <li><p>Don't <code>require</code> files using <code>__FILE__</code>.</p></li> <li><p>Don't rely on anything outside the load path. Folders may not have the same structure as in your original version. For example, don't use something like </p> <p>VERSION = ::File.read(::File.join(::File.dirname(<strong>FILE</strong>), "..", "..", "VERSION")).strip</p></li> <li><p>Don't manage <code>$LOAD_PATH</code> within <code>lib</code>.</p></li> <li><p>Provide a <code>VERSION</code> constant.</p></li> <li><p>Don't depend on rubygems. The person using your code may not be using rubygems, but some other packaging system (or no packaging system). Similarly, don't mention version dependencies in the code itself, or <code>rescue Gem::LoadError</code>.</p></li> </ul> <p><a href="https://oree.ch/2009/06/06/rubygems-dependencies.html" rel="nofollow noreferrer">Rubygems dependencies. Please...</a> argues that you shouldn't list optional runtime dependencies, and should separate developer from runtime dependencies.</p> <p><a href="http://github.com/agrimm/zombie-chaser/commit/0a888b2ea33481e078ab7640c9fd38dc6a23710f" rel="nofollow noreferrer">From my own experience</a>: if nothing else, try building and installing your gem locally before releasing it into the wild. It avoids brown paper bag releases.</p>
    singulars
    1. This table or related slice is empty.
    1. POGotchas for writing rubygems
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAndrew Grimm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGotchas for writing rubygems
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODefinitely a good and correct writeup, especially with the reference to "Gem Packaging: Best Practices"
      singulars
      1. PO
      1. USDominik Honnef
    2. COYour last point is very important. It could basically be rephrased as: "One important gotcha for writing Ruby Gems is not to write Gems, write libraries."
      singulars
      1. PO
      1. USJörg W Mittag
    3. CO@Jörg: Very Zen-like. (The last point from "Gem Packaging: Best Practices" that is, not the "From my own experience")
      singulars
      1. PO
      1. USAndrew Grimm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload