// Tutorial //

Meteor Special Directories

Published on December 29, 2015
    Default avatar
    By Alligator.io
    Developer and author at DigitalOcean.
    Meteor Special Directories

    While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.

    Unlike in Rails, Meteor projects don’t have a rigid file structure and you are pretty much free to organize your projects as you want. A few folder names however have special meaning, and files within them will be treated differently.

    client

    Files here will be loaded on the client only. Files in that folder don’t need things like Meteor.isClient.

    server

    Loaded on the server only, duh! No need for Meteor.isServer when files are in that folder, the client won’t see these files.

    public

    This directory is for assets like images. In your projects, you reference stuff in the public folder as if they were in the root folder. For example, if you have a file: public/nude.jpg, then in your app you include it with <img src=“nude.jpg”>.

    private

    Files only accessible on the server side through the Assets API.

    tests

    Files in there won’t be loaded anywhere and are used for testing your app.

    lib

    Files in that folder are loaded before anything else, which makes it the perfect directory to place the different libraries used on a project.


    Want to learn more? Join the DigitalOcean Community!

    Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in our Questions & Answers section, find tutorials and tools that will help you grow as a developer and scale your project or business, and subscribe to topics of interest.

    Sign up
    About the authors
    Default avatar
    Developer and author at DigitalOcean.

    Still looking for an answer?

    Was this helpful?
    Leave a comment