<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Meteor on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/meteor/</link>
    <description>Recent content in Meteor on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Mar 2017 16:20:06 +0000</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/meteor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Meteor project structure</title>
      <link>https://janikvonrotz.ch/2017/03/28/meteor-project-structure/</link>
      <pubDate>Tue, 28 Mar 2017 16:20:06 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2017/03/28/meteor-project-structure/</guid>
      <description>&lt;p&gt;Get the latest version of this specification here: &lt;a href=&#34;https://gist.github.com/d4755eb1b7a9d6b08515408ea6fd69bb&#34;&gt;https://gist.github.com/d4755eb1b7a9d6b08515408ea6fd69bb&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The Meteor project structure (MPS) is a proposal for a simple file and folder naming specification.&lt;/p&gt;&#xA;&lt;p&gt;There are several basic distinctions when building a Meteor project structure. First there is a &lt;strong&gt;client&lt;/strong&gt;, &lt;strong&gt;server&lt;/strong&gt; and an &lt;strong&gt;imports&lt;/strong&gt; folder. All folders have specific naming rules and differ in their structure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploy your Meteor app with PM2</title>
      <link>https://janikvonrotz.ch/2017/03/14/deploy-your-meteor-app-with-pm2/</link>
      <pubDate>Tue, 14 Mar 2017 14:12:42 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2017/03/14/deploy-your-meteor-app-with-pm2/</guid>
      <description>&lt;p&gt;PM2 is a well-known node process manager. Not so well-known is its deployment feature. With pm2 you can reasonable easy deploy any node application. As Meteor is always a node app at its heart I&amp;rsquo;ve decided to deploy my current Meteor project with PM2.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor register LDAP login request handler</title>
      <link>https://janikvonrotz.ch/2017/02/08/meteor-register-ldap-login-request-handler/</link>
      <pubDate>Wed, 08 Feb 2017 20:53:56 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2017/02/08/meteor-register-ldap-login-request-handler/</guid>
      <description>&lt;p&gt;One requirement for my current Meteor project was that a user must login with their ActiveDirectory account. This means that Meteor must be able to authenticate against LDAP. In atmosphere there are already a few packages available which implement and support LDAP authentication. However, they are either outdated or difficult to configure. This is why I&amp;rsquo;ve decided to build my own custom login request handler for Meteor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Authenticate Meteor accounts with the Apollo GraphQL API</title>
      <link>https://janikvonrotz.ch/2016/11/12/authenticate-meteor-accounts-with-the-apollo-graphql-api/</link>
      <pubDate>Sat, 12 Nov 2016 10:21:20 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/11/12/authenticate-meteor-accounts-with-the-apollo-graphql-api/</guid>
      <description>&lt;p&gt;One of the popular features of Meteor is its accounts package. As you know, it makes it fairly easy to add a user authentication solution to your Meteor app or add support for different oAuth services. With the possibility to integrate an Apollo GraphQL API into your Meteor app this became a bit more difficult. The Apollo stack does not support an out of the box solutions to authenticate users with Meteor accounts. Jonas Helfer, one of the Apollo core devs, proposed &lt;a href=&#34;https://dev-blog.apollodata.com/a-guide-to-authentication-in-graphql-e002a4039d1&#34;&gt;two ways to authenticate users with your app&lt;/a&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Graphql with Apollo, Meteor and React</title>
      <link>https://janikvonrotz.ch/2016/10/09/graphql-with-apollo-meteor-and-react/</link>
      <pubDate>Sun, 09 Oct 2016 19:39:30 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/10/09/graphql-with-apollo-meteor-and-react/</guid>
      <description>&lt;p&gt;For my last project I had to build a web application to administrate a MongoDB database. Due to using Meteor quite a lot I heard about Graphql and the Apollostack. Graphql, which is a specification done by Facebook engineers, promises to be the better REST API (which I hope it is). I became curious and decided the build the server API with Apollo. First I tried to evade using the Meteor as build system as I don&amp;rsquo;t want to get too accustomed to this full-stack ecosystem. However, building a live-reload server and client build system in ES6 with Node.js, Babel and Webpack was simply too much work compared to building this simple web app. So in result this was my stack:&lt;/p&gt;</description>
    </item>
    <item>
      <title>OLMOTO - An app built by beginners</title>
      <link>https://janikvonrotz.ch/2016/08/02/olmoto-an-app-built-by-beginners/</link>
      <pubDate>Tue, 02 Aug 2016 12:30:05 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/08/02/olmoto-an-app-built-by-beginners/</guid>
      <description>&lt;p&gt;One month ago I started teaching a friend the basics of JavaScript with Meteor, Mantra and React.&#xA;Together we&amp;rsquo;ve built an app to create and share events with friends. It was an awesome experience. Yesterday we launched a private version on heroku. For us this was a great accomplishment. I learned a lot from this project and thought about sharing it with world.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://codeberg.org/janikvonrotz/olmoto&#34;&gt;https://codeberg.org/janikvonrotz/olmoto&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Some technical features and challenges we solved:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor create user with a profile and custom attributes</title>
      <link>https://janikvonrotz.ch/2016/07/11/meteor-create-user-with-a-profile-and-custom-attributes/</link>
      <pubDate>Mon, 11 Jul 2016 20:34:48 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/07/11/meteor-create-user-with-a-profile-and-custom-attributes/</guid>
      <description>&lt;p&gt;For Meteor there are not many options left when choosing a user account package. The built-in option is the only use- and successful solution so far. The package is well documented and works like a charm. However, whenever I set up the account system in Meteor I am confronted with these two scenarios:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How can I extend the user profile object with data from a registration form? (A user should be able to edit the profile data himself later on.)&lt;/li&gt;&#xA;&lt;li&gt;And how can I add other attributes to the user collection object? (A user should not be able to change a custom attribute himself later on.)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;These are two fundamental obstacles almost every developer faces when setting up the account system. There are a lot of solutions out there on how to do this in Meteor properly, but a lot of them are poorly described and make it difficult the get the right idea of how the account system works. It got even more difficult due  to API changes and Meteor itself that changed a lot over years. Now I would like to give a good example for this two questions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor productive deployment blank page</title>
      <link>https://janikvonrotz.ch/2016/06/21/meteor-productive-deployment-blank-page/</link>
      <pubDate>Tue, 21 Jun 2016 10:16:07 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/06/21/meteor-productive-deployment-blank-page/</guid>
      <description>&lt;p&gt;First some background. I&amp;rsquo;ve built a Meteor app and decided to deploy it to Heroku. There are many short and simple guides out there on how to do that. As I did so and opened the App for the first on Heroku I simply received a blank page. Where did my javascript code go? Heroku logs didn&amp;rsquo;t tell much.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor and Mantra - Routing redirect</title>
      <link>https://janikvonrotz.ch/2016/05/26/meteor-and-mantra-routing-redirect/</link>
      <pubDate>Thu, 26 May 2016 10:03:22 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/05/26/meteor-and-mantra-routing-redirect/</guid>
      <description>&lt;p&gt;Recently I started using &lt;a href=&#34;&#34;&gt;Mantra&lt;/a&gt; to develop my Meteor apps. As with any other framework You&amp;rsquo;ll find a lot of answers to common questions in a related forum or any other resource. However I couldn&amp;rsquo;t get a good answer on how to implement routing logic properly. The Mantra specs also don&amp;rsquo;t tell much about how to approach it. So here&amp;rsquo;s my solution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor and React: Markdown editor with draft.js and marked.js</title>
      <link>https://janikvonrotz.ch/2016/04/05/meteor-and-react-markdown-editor-with-draft-js-and-marked-js/</link>
      <pubDate>Tue, 05 Apr 2016 09:15:29 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/04/05/meteor-and-react-markdown-editor-with-draft-js-and-marked-js/</guid>
      <description>&lt;p&gt;Recently I switched my current project from Meteor 1.2 to 1.3. While doing so I reworked the code for my markdown editor. When created the markdown editor in the first place I learned about the necessity of a solid platform to build web editors. So this time I used draft.js as base. Facebook open sourced draft.js a few months ago. They use it almost everywhere on Facebook page, so it should be well-tested.&lt;/p&gt;&#xA;&lt;p&gt;The markdown editor you&amp;rsquo;re going to build has these features:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Instant html preview rendering&lt;/li&gt;&#xA;&lt;li&gt;Support for GitHub flavoured syntax and markdown tables&lt;/li&gt;&#xA;&lt;li&gt;Drag and drop file upload.&lt;/li&gt;&#xA;&lt;li&gt;Copy and paste file upload.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Optionally: File upload with Meteor and FS Collection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor and React: Fullscreen Viewer Component</title>
      <link>https://janikvonrotz.ch/2016/03/08/meteor-and-react-fullscreen-viewer-component/</link>
      <pubDate>Tue, 08 Mar 2016 15:51:29 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/03/08/meteor-and-react-fullscreen-viewer-component/</guid>
      <description>&lt;p&gt;Another post as result of my Meteor React experience.&#xA;This is a simple approach to build a fullscreen viewer for any React component.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor and React: Bootstrap Modal</title>
      <link>https://janikvonrotz.ch/2016/03/05/meteor-and-react-bootstrap-modal/</link>
      <pubDate>Sat, 05 Mar 2016 12:42:05 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/03/05/meteor-and-react-bootstrap-modal/</guid>
      <description>&lt;p&gt;I would like to share my great experience I had with Meteor and React. This time I want to show how I&amp;rsquo;ve built a bootstrap modal component. There are already a lot of solutions out there, but none of them were suitable.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s how you can get a neat bootstrap modal for your Meteor React project.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meteor White Paper</title>
      <link>https://janikvonrotz.ch/2015/12/16/meteor-white-paper/</link>
      <pubDate>Wed, 16 Dec 2015 21:05:20 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2015/12/16/meteor-white-paper/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;Today&amp;rsquo;s internet would not work without web applications. Web applications made the web dynamic and extended its targeted audience. The applications made it possible for companies to create new business models and sell their goods and services online. They became popular due to the ubiquity of web browsers, and the convenience of using a web browser as a client (Wikipedia, 2015). Undoubtedly, the technology to build web applications is the cornerstone to enabling the enterprises to keep up with the pace of business. Life cycles of products have become shorter while the demand raised at the same time. Enterprises have to accelerate their application development process to stay competitive in the future.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
