Corrie | directly creates a PowerPoint presentation | Development Tools library

Set vertical-align: top to .gallery.grid li. Like this:

I think this could work:

There is perhaps very many ways to solve this, but in my opinion the easiest way is to simply do a search in the data structure and store the IDs in inverse order of when you find them. This way the output is what you are after.

You could also just reverse the ordering of a different approach.

I would like to note that the json-structure is a bit weird. I would have expected it to simply have nested children arrays, and not have them renamed parent, children, and grandchildren.

Without going into a lot of detail about automated building procedures, the steps usually go as follows:

• Build Code -- Here, your source code is built and transpiled into a distributable format, which usually goes into a dist/ folder.

• Upload your distributable code. -- Here, all of the files you have built should be uploaded (manually or automatically) to your EC2 instance.

• Run a startup script -- Here, any project startup code should be run in order to actually start your server.

You don't need babel in production because your project should already have been built by that point. However, if you are building on the EC2 instance, instead of just uploading your dist, then you will need it.

In order to turn your EC2 into a routable, reachable web server, you will need to configure some security and routing policies on AWS. You will need to ensure that the instance has a routable IP (or you can use the automatically generated DNS provided by AWS). Secondly, you'll need to ensure that your security policy allows port 80 (at the very least, and any additional ports you need to interact with the server - for HTTPS, SSH or something else.)

Once you have all this in place, you should be good.

EDIT

If you want to serve static HTML pages, you will have to ensure that you have set up your EC2 container as a web server with something like Apache. However, I would recommend that you run your Node Server exclusively from the server and host your static webpack bundle on S3 as a static website.

EDIT 2

• Here's an introduction to setting up your EC2 instance for node. - https://medium.com/@nishankjaintdk/setting-up-a-node-js-app-on-a-linux-ami-on-an-aws-ec2-instance-with-nginx-59cbc1bcc68c
• Here's an introduction to setting up a static website with S3. - https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html

1. Field promotion may solve hotspotting. Still, wouldn't that make querying by time range a little bit difficult?

That depends what your query looks like. For example, if you want to query Corrie's battery status from T1 to T2, you can construct a row range easily: [BATTERY#Corrie#T1, BATTERY#Corrie#T2]. However, if you want to query the battery status of all the users, then all the rows with prefix BATTERY will be scanned.

So, the most important queries you have should dictate which fields you promote to the row key. Also, fields with high cardinality help more when promoted to row key, as they distribute load to a larger number of tablets.

1. On the other side, is hotspotting avoidable if you want to query a range ONLY by TIMESTAMP? Don't think so, right?

I am not entirely sure what you mean by "query a range only the timestamp", can you provide an example?

A lot will depend on what "TIMESTAMP" means. If you always want to query for last 10 minutes, then all of your queries will go to a single server at any given time and you will experience hotspotting.

Another thing to keep in mind is that if you don't design the row key properly, writes will encounter hotspotting and you will not get good write throughput. Its recommended to design row-keys to avoid hotspotting.

Since you added relationship between your nodes, the query can be greatly simplified.

We need paths from each instructor to child instructors up to 3 levels down, and depending on how far down, we can get the appropriate percentage to run the calculations on the given transactions, then sum it all up.

Here's an example query that should work, though it will report on any instructor with at least one child instructor, instead of only instructors with at least 3 levels down of child instructors.