Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The best solution I've found to this is not to use the asset pipeline for HTML template files. </p> <p>Instead make a controller called <code>TemplatesController</code> and create only one action. Then map all template URLs to that using a route such as:</p> <pre><code>get /templates/:path.html =&gt; 'templates#page', :constraints =&gt; { :path =&gt; /.+/ } </code></pre> <p>Then move all the template files into <code>app/views/templates</code></p> <p>Then inside the controller, setup the following:</p> <pre><code>caches_page :page def page @path = params[:path] render :template =&gt; 'templates/' + @path, :layout =&gt; nil end </code></pre> <p>This way all of your template files will be served from the controller and then will be cached into public/templates. To avoid cache problems, you can create a timestamp path into the template route so that your cached files are delivered with a version:</p> <pre><code>get '/templates/:timestamp/:path.html' =&gt; 'templates#page', :constraints =&gt; { :path =&gt; /.+/ } </code></pre> <p>This way you can have a new timestamp each time you upload the website and you can store the templates folder anywhere you like. You can even store the templates folder on S3 and have an assets URL for that. Then wherever your template files are addressed, you can use a custom asset method:</p> <pre><code>templateUrl : &lt;%= custom_asset_template_url('some/file.html') %&gt; </code></pre> <p>Where:</p> <pre><code>def custom_asset_template_url(path) "http://custom-asset-server.website.com/templates/#{$some_global_timestamp}/#{path}" end </code></pre> <p>Then just make the asset redirect to the Rails server if it's not found and it will be generated. Or all template files can be pre-generated once uploaded.</p>
    singulars
    1. This table or related slice is empty.
    1. PORails static html template files in the asset pipeline and caching in development mode
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmatsko
    1. USmatsko
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORails static html template files in the asset pipeline and caching in development mode
      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. VTAcceptedByOriginator
    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. COThat solution is ok, because it works. However it doesn't work as good as for other assets - it lacks the caching with fingerprinting.
      singulars
      1. PO
      1. USmateusz.fiolka
    2. COThe major tradeoff is that you if you continue using the assets directory to deliver template files then you do not have access to `partials`, `routes`, `url helpers` and `any other shared Rails code`. You also have to manually "touch" the HTML files each time you change them. While it's nice to have fingerprinted files within your assets, the problem then becomes having to upload those asset files each time you deploy. You will also need to create a CORS policy for your asset files since it's likely that your templates will be delivered by a CDN. You can see why I chose to do it this way.
      singulars
      1. PO
      1. USmatsko
    3. COThis solution is really great! There is an error though: you define a route to the action file, but in the controller you are using the action page.
      singulars
      1. PO
      1. USyagooar
 

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