James Nine's questions

I'm unable to deploy code on Elastic Beanstalk CLI for some odd reason. I'm using CodeCommit, and after a long while, it errors out and gives me the following:

Starting environment deployment via CodeCommit
--- Waiting for Application Versions to be pre-processed ---
ERROR: All application versions have not reached a "Processed" state. Unable to continue with deployment.

Then it just ends. I'm unable to use the commands eb create nor eb deploy. I'm not sure what the error means by not reaching a "Processed" state... At the time of this writing, I only have one application and one environment, and it's current status is "OK" (green), as it's our main website and it's running fine. I just want to do a code update to it, but I'm unable to.

Now the only way I can deploy it is via the GUI, by going into the Application Versions page and clicking on Deploy. But I used to be able to do it fine on the EB CLI.

I've tried to do a search for that specific error but have yielded nothing useful.

I'm really new to AWS ELB and I'm reading about how to automatically mount an EBS volume from a snapshot via the ebextensions script. I've found this post as a reference: https://aws.amazon.com/blogs/devops/customize-ephemeral-and-ebs-volumes-in-elastic-beanstalk-environments/

But basically, my question is, how do I set in the option settings to have it automatically pull the latest snapshot id? Because the snapshots will be updated daily, and I only want to get the latest snapshot without having to edit the ebextensions script each time.

This is what I'm thinking the ebextensions script will be:

commands:
  01mkdir:
    command: "mkdir /mnt/ebs_snapshot"
  02mount:
    command: "mount /dev/sdh /mnt/ebs_snapshot"
option_settings:
  - namespace: aws:autoscaling:launchconfiguration
    option_name: BlockDeviceMappings
    value: /dev/sdh=(how to put latest snapshot id?)

I also found this post: http://www.commandlinefu.com/commands/view/13514/find-the-most-recent-snapshot-for-an-aws-ebs-volume

But not sure how to incorporate that into the ebextensions script file...

I need to rewrite a bunch of urls (about 100 or so) for SEO purposes, and there may be more being added in the future (probably another 50-100 later on). I need a flexible way of doing this and so far, the only way I can think of is to edit the .htaccess file using the rewrite engine.

For example, I have a bunch of urls like this (please note that the query string is irrelevant, and dynamic; it could be anything. I was only using them purely as an example. I am only focusing on the pathname--the part between the hostname and query string, as marked in bold below):

http://example.com/seo_term1?utm_source=google&utm_medium=cpc&utm_campaign=seo_term http://example.com/another_seo_term2?utm_source=facebook&utm_medium=cpc&utm_campaign=seo_term

http://example.com/yet_another_seo_term3?utm_source=example_ad_network&utm_medium=cpc&utm_campaign=seo_term http://example.com/foobar_seo_term4

http://example.com/blah_seo_term5?test=1

etc...

And they are all being rewritten to (for now): http://example.com/

What's the most efficient/effective way of doing this so that I may be able to add more terms in the future?

One solution I came across is to do this (in the .htaccess file):

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ / [NC,QSA]

However, the problem with this solution is that even invalid urls (such as http://example.com/blah) will be rewritten to http://example.com instead of giving a 404 code (which is what it is supposed to do anyway). I'm still trying to figure out how all this works, and the only way I can think of is to write 100 more RewriteCond statements (such as: RewriteCond %{REQUEST_URI} =/seo_term1 [NC,OR]) before the RewriteRule directive. For example:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} =/seo_term1 [NC,OR]
RewriteCond %{REQUEST_URI} =/another_seo_term2 [NC,OR]
RewriteCond %{REQUEST_URI} =/yet_another_seo_term3 [NC,OR]
RewriteCond %{REQUEST_URI} =/foobar_seo_term4 [NC,OR]
RewriteCond %{REQUEST_URI} =/blah_seo_term5 [NC]
RewriteRule ^(.*)$ / [NC,QSA]

But that doesn't sound very efficient to me. Is there a better way?

I have setup mod_rewrite and mod_alias on Apache2 on Debian (in a test server).

I have the following rewrite code in /etc/apache2/sites-available/default:

<Directory />
  Options FollowSymLinks
  AllowOverride All
  RewriteEngine on
  RewriteCond %{REQUEST_URI} !\.(php|html|css|js|gif|png|jpe?g)$
  RewriteRule (.*)$ /index.php [L]
</Directory>

I have the following alias code that is setup by default from the phpmyadmin package (loaded via apt-get install phpmyadmin and located in /etc/apache2/conf.d/phpmyadmin.conf):

Alias /phpmyadmin /usr/share/phpmyadmin

Everytime I load http://my.test.server/phpmyadmin, it goes to http://my.test.server/index.php and not the alias (which is bypassed/ignored?).

How do I setup an exclusion rule to allow aliases to pass through (even if the alias is setup in a different file?)

I have been dabbling with Node.js lately, and I came across this article on how to get it to start automatically after a reboot:

http://howtonode.org/deploying-node-upstart-monit

In particular, the article recommends that I use upstart (I'm running Debian Squeeze). I've been able to install upstart fine, and when I use the "start" and "stop" commands, everything works perfect. However, whenever I reboot, Node.js never runs. The log is empty and I can't figure out why it's not working. I'm ready to give up on upstart, but I want to know if anyone else is having the same issue?

Here is my upstart script:

description "node.js server"
author      "me"

start on (local-filesystems and net-device-up IFACE=eth0) 
# i also tried "start on startup", still does not work.
stop on shutdown

respawn
respawn limit 5 60

script
exec sudo -u node sh -c "/usr/local/bin/node /opt/apps/firstapp/app.js >> /var/log/firstapp.log 2>&1"
end script