Hi Joel, regarding the behavior you mentioned earlier, where not all of
your resources loaded because the server froze up:
What happened was you maxed-out the 1gb of RAM that your t2.micro instance
has. I've described this before in this thread
Hi Adam,
Thanks for letting me know. I actually thought about it when it happened
because my instance is very small so I will just increase my instance size
the next time I'm uploading resources. I have a few thousands more to
upload in the next few months so I would keep that in mind.
Regards,
Joel,
Check the data.edit_log table of your arches database. This is where arches
keeps the load_id and edit information for resources. You can find the
load_id in the 'note' column of this table. It's probable that even though
your initial load did not finish the load_id of the initial load
