Usually this has already been halted a long time ago anyway, and our own DB is just out of sync.

There's not a 1:1 mapping from users to instances of course, so we might want to further subdivide it like technomancy.4.syme.in or something.

Needs styling. Also need to mention on that page that Syme only works with public repos.

When trying to launch a new session for collaboration syme reports an error. The provided ssh command does not work, although the EC2 instance is started when investigating my AWS console. Trying to halt from the syme UI does not work. This was also reproduced by @hlatki. This was all seen via the heroku app running at: https://syme.herokuapp.com/

This will make it easier to tell when you accidentally add the wrong user. But it needs some jabbascript. Auto-completion would be great too!

Or just leave it up to the user to IM them or something. If we do email automatically, we should leave a checkbox so you can turn it off.

This could go on the splash page if you're logged in, but we'd have to rearrange it to make room. One suggestion of how it could be rearranged.

We don't clean up the instances table properly, so if you start and halt an instance it won't let you start another.

Currently if you close your browser and return to an instance page, you won't be able to halt it since your browser doesn't have the creds cookie. You'd need to launch a new instance to create the cookie, which doesn't make sense.

Prompting for creds if it's not there when halting would probably still be a good idea though.

Not sure if this is possible, but if so it would be great to refuse to shutdown if unpushed changes are present.

The biggest annoyance with Syme is waiting for bootstrap. The longest steps in bootstrapping are installing packages, so an AMI that ships with these packages out of the box would be less annoying:

• git
• tmux
• emacs24-nox
• vim-nox
• openjdk-7-jre-headless (this one takes forever to install)
• round it out with curl, tree, zip, unzip, possibly rubygems

Adding a Mumble server would allow for hassle-free voip, though the security group would have to be modified to open the port for it.

You don't want to expose your SSH agent to other users, even if you're pairing with them. We could warn people, but it would be better to block it at a server level.

This will also require performing clones using HTTPS git and pushing with a password.

After the post-boot setup failed on me (not sure why) the terminate button on the UI disappeared. I was able to get it back by refreshing the page and playing catch-a-button before it disappeared again.

Usually the instance is able to be created successfully, but only the ubuntu user is created and no actions are run.

Need some JS magic here

Running on Chrome on OSX.

When I enter a comment on a post, return or enter does nothing. Tab leaves the comment field but does not submit it. Any attempt to leave the page displays the popup about having unsaved changes.

Did I miss something?

https://www.evernote.com/shard/s3/sh/6c7c6be1-a800-4924-a21a-a4d7bf5f52d0/6d816c60398e44e699c0833208817937

The instance is still accessible via the AWS IP or hostname, though. Hopefully it's simply a DNS issue or an issue with the AWS credentials used to manipulate route53.

Might want to automate checking out dotfiles for the owner so they don't have to manually grab all their marmalade packages, bashrc, etc.

Or maybe not; this can be done easily enough client-side.

Even upon successful convergenge, /etc/motd is always empty.

Strange because /etc/tmux.conf is set, and they are populated the exact same way.

Question more than an issue - and a newbie one at that.

I successfully invited myself and one other to a project (keithmantell/cljtpc).

• What am I meant to see when things are setup? When I ssh in I can see only syme and ubuntu under home and not much in each.
• Should the surce code from the github project be somewhere?
• I went so far as to add a bootstrap (for instance install emacs24-nox), .profile etc. but none of that appears to have been used.

I am probably missing something simple - if I should ask this level of question elsewhere, let me know.

Keith

Set up a shutdown notification endpoint that can be invoked when the instance shuts down. It should require a unique token so it can only be invoked by the instance.

http://askubuntu.com/questions/30383/best-way-to-make-a-shutdown-hook

Install the shutdown hook via userdata.sh and have it hit the endpoint with curl.