
Included in the resources you will find express.js
Use as shown in the lecture to test if Node.js/Express was installed correctly
The bare minimum needed to use the IIS web server
A short overview of the basic Parse methods we will be using in the "Importing data into Parse" lecture
Included in the resources you will find parse-server.js
Use as shown in the lecture to test if Parse Server was installed and runs correctly.
You can also use parse-server.bat to run Parse Server.
If you would like to set up Parse Server to run automatically, you can do the following:
- Download parse-server.bat to the server desktop
- Create a shortcut to parse-server.bat as follows:
o Right-click on the downloaded file parse-server.bat
o Click on Send to
o Click on Desktop (create shortcut)
- Copy the shortcut to folder
C:\Users\e2eServer\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
Please note that later on we will be running parse-server.js to use Parse Dashboard and Redis Server as well.
You will need to uncomment relevant lines to test if each were installed and run correctly.
Here is an example of how those lines appear in the code:
// uncomment the next line to start using parse-dashboard
// var ParseDashboard = require('parse-dashboard');
After uncommenting the relevant lines, use parse-server.js as shown in the lecture
Parse Dashboard is run from within parse-server.js
You will need to uncomment relevant lines to test if Parse Dashboard has been installed correctly.
Here is an example of how those lines appear in the code:
// uncomment the next line to start using parse-dashboard
// var ParseDashboard = require('parse-dashboard');
After uncommenting the relevant lines, use parse-server.js as shown in the lecture
import2parse.js is a simple script that serves as an example of how you can import data in JSON format into Parse Server and MongoDB. The script is general, but not generic. Should you decide to use it beyond the scope of the example shown in this lecture, you will need to make adjustments and perform the necessary acceptance tests.
In this lecture you will see an example of importing data from Google's Firebase database to Parse.
Firebase is a Google Cloud Platform serverless real-time database which can evolve into a risk as a result of vendor lock-in as well as design, performance and security issues. Most regulated institutions will not allow their data to exist on a serverless platform outside of their corporate network, but you can still offer your clients a very similiar solution by using Parse, Redis and Mongo together.
This lectures shows how you can migrate your application data from Firebase to your own secure Parse Server . If you run into any difficulties, please let me know and I will do my best to help.
Includes a short introduction on memory caching and how Parse uses Redis as its' cache adapter.
Redis Server runs seperately from Parse Server.
Use this link https://github.com/ServiceStack/redis-windows to get to the ServiceStack resources for setting up Redis on Windows.
You can use redis-server.bat to run Redis Server.
If you would like to set up Redis Server to run automatically, you can do the following:
- Download redis-server.bat to the server desktop
- Create a shortcut to redis-server.bat as follows:
o Right-click on the downloaded file redis-server.bat
o Click on Send to
o Click on Desktop (create shortcut)
- Copy the shortcut to folder
C:\Users\e2eServer\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
Working with the Redis client -
- Add the Redis client to your app via npm install --save redis
- Run redis-test.js to see that you can perform the basic set/get functions
Defining Redis as the cache adapter for Parse Server in parse-server.js -
You will need to uncomment relevant lines to test if it has been defined correctlly.
Here is an example of how those lines appear in the code:
// uncomment the next line to start using redis
// var RedisCacheAdapter = require('parse-server').RedisCacheAdapter;
After uncommenting the relevant lines, use parse-server.js as shown in the lecture
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
The files for lectures 24-27 are located in lecture 27.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
The files for lectures 24-27 are located in lecture 27.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
The files for lectures 24-27 are located in lecture 27.
Please note that the files in the resources should not be copied directly into your project folders.
They should be used as an auxiliary reference for the code you will be developing.
The files for lectures 24-27 are located in lecture 27.
Welcome to the first tutorial in the Works-Like-A-Charm series - the goal of this course is to enable you to get a better understanding of the End-to-End FullStack puzzle.
The course is short and concise, and is more about architecture than about code. You will learn how to make it happen using an Ionic/Angular Frontend & Parse/Redis/MongoDB on NodeJS/Express Backend, and you will discover the benefits that can be gained with this technology stack: One code base - for both Frontend and Backend; The Power of RxJS - to enable realtime, live, responsive data; The Power of Memory Caching - a simple technique that you can implement on your own; Take Control - create a viable alternative from dependency on cloud-only solutions like Firebase.
You will go into the important aspects of the code so you should have some experience with web development, preferably with Javascript frameworks like Angular or Ionic. The course emphasizes the practical side of setting up a real-world environment: creating your own client and server virtual machines; implementing advanced techniques like Observables, memory caching and generic data services; and leveraging the Frontend and Backend components together to create a simple yet powerful architecture that you can rely on to deliver performant and realtime applications.