Week 1: 0%
Week 2: 100%
Week 3: 20%
My current integrity is 40%. If this is a war, there are 12-13 "battles". So far, you've lost more than half of them. You can't be putting up "20s" in your third week. You are LOSING this war.
This weeks goals -- same as last week.
1. Complete implementation of Salient web theme. This is the primary objective.
2. Begin creating my website's content (tweaking the theme, getting the video and opt-in on there, etc.)
3. See if I can, and if possible, begin recovery and transfer of all worthwhile content from HostGator.
You have a head start. Do whatever it takes to win. PLAN TO WORK THIS FRIDAY TO HELP UN-DO THE DAMAGE FROM SUNDAY... DON'T LET THAT FAILURE STACK!!
---
Appearently, my new wordpress server is linux / unix, therefore, if I am to tweak anything, I may need to use Unix:
BASIC UNIX COMMANDS: http://mally.stanford.edu/~sr/computing/basic-unix.html
Fortunately, I have been trained in the most basic ideas behind how DOS works, so I have an idea of what to do.
NEXT QUESTION:
-Should I be interfacing my EC2 instance with S3? Do I just put salient in there and run it from S3?? Or do I put everything on the Linux server and install it with Unix?
ANSWER:
-YES -- easiest way for me looks like interfacing with S3, but that's not the "standard" way to do it.
When you launch wordpress with AWS on a "stack", you're setting up a server, whether you use unix or windows server, all the files are going to your virtual server.
So by default, you edit the core of your site (like putting the Salient theme in there) via a SSH Unix connection. Basically, bitch is ugly.
But instead of running everything through Unix, why not use S3 instead by setting it up as the CDN for all your files?
CDN is content delievery network, which is essentially a cloud of servers across the world. Which is what S3 already is. So if you simply configure Amazon's Cloud Front to use S3, you can then pull all the necessary files directly from s3 into wordpress by using wordpress "cache" plugins.
Here's the tutorials:
1. http://www.webdesignerdepot.com/2013/08/how-to-take-wordpress-to-the-cloud-with-amazon-s3-cloudfront/
2. https://ulrich.pogson.ch/setup-aws-work-amazon-s3-wordpress-plugin
3. https://wordpress.org/support/topic/wordpress-can-now-run-on-amazon-s3
(for more "How to", see GOOGLE... I only just started down this path. I don't know if you'll need to learn more first or not.)
I think what that means is
1 -- I take my current wp temp site and install a cache plugin.
2 -- I put my theme and other stuff I want on my WP and put it on S3
3 -- I set Amazon cloudfront to interface my S3 with WP
4 -- I go into wordpress and make the magic happen right inside there. And anything I'm missing can simply be added into S3.
I imagine true root changes to WP still require I go into Linux.
---
Okay well tonight I spent 3 hours:
-Reviewing and upgrading my word. Had to get serious and be honest with my short comings, and I discovered the Word Burier troll. Learned to be very aware of letting failures stack, as this very thing is causing the renaissance to fail
-Learning how to get into my "stack" or server, as well as the basics like making directories, deleting files, and basic navigation on Unix. Still don't know where they are hiding WP though.
-Learned where to start so far as hosting my WP theme and files from S3 through Cloudfront CDN so I don't have to put everything on a Unix server. Because I really don't want to be going into the Unix server unless I have no other choice.
2. Begin creating my website's content (tweaking the theme, getting the video and opt-in on there, etc.)
3. See if I can, and if possible, begin recovery and transfer of all worthwhile content from HostGator.
You have a head start. Do whatever it takes to win. PLAN TO WORK THIS FRIDAY TO HELP UN-DO THE DAMAGE FROM SUNDAY... DON'T LET THAT FAILURE STACK!!
---
Appearently, my new wordpress server is linux / unix, therefore, if I am to tweak anything, I may need to use Unix:
BASIC UNIX COMMANDS: http://mally.stanford.edu/~sr/computing/basic-unix.html
Fortunately, I have been trained in the most basic ideas behind how DOS works, so I have an idea of what to do.
NEXT QUESTION:
-Should I be interfacing my EC2 instance with S3? Do I just put salient in there and run it from S3?? Or do I put everything on the Linux server and install it with Unix?
ANSWER:
-YES -- easiest way for me looks like interfacing with S3, but that's not the "standard" way to do it.
When you launch wordpress with AWS on a "stack", you're setting up a server, whether you use unix or windows server, all the files are going to your virtual server.
So by default, you edit the core of your site (like putting the Salient theme in there) via a SSH Unix connection. Basically, bitch is ugly.
But instead of running everything through Unix, why not use S3 instead by setting it up as the CDN for all your files?
CDN is content delievery network, which is essentially a cloud of servers across the world. Which is what S3 already is. So if you simply configure Amazon's Cloud Front to use S3, you can then pull all the necessary files directly from s3 into wordpress by using wordpress "cache" plugins.
Here's the tutorials:
1. http://www.webdesignerdepot.com/2013/08/how-to-take-wordpress-to-the-cloud-with-amazon-s3-cloudfront/
2. https://ulrich.pogson.ch/setup-aws-work-amazon-s3-wordpress-plugin
3. https://wordpress.org/support/topic/wordpress-can-now-run-on-amazon-s3
(for more "How to", see GOOGLE... I only just started down this path. I don't know if you'll need to learn more first or not.)
I think what that means is
1 -- I take my current wp temp site and install a cache plugin.
2 -- I put my theme and other stuff I want on my WP and put it on S3
3 -- I set Amazon cloudfront to interface my S3 with WP
4 -- I go into wordpress and make the magic happen right inside there. And anything I'm missing can simply be added into S3.
I imagine true root changes to WP still require I go into Linux.
---
Okay well tonight I spent 3 hours:
-Reviewing and upgrading my word. Had to get serious and be honest with my short comings, and I discovered the Word Burier troll. Learned to be very aware of letting failures stack, as this very thing is causing the renaissance to fail
-Learning how to get into my "stack" or server, as well as the basics like making directories, deleting files, and basic navigation on Unix. Still don't know where they are hiding WP though.
-Learned where to start so far as hosting my WP theme and files from S3 through Cloudfront CDN so I don't have to put everything on a Unix server. Because I really don't want to be going into the Unix server unless I have no other choice.
No comments:
Post a Comment