Website for customer Katoeys 'Are' Us (Pattaya, Thailand)


  • Because servers. Lots of them. Lots of configurations. Great for mission-specific functions. Video encoding, data aggregation, dedicated processing, mission-critical data stores. Anything you can't hang off your Heroku environment.


  • Human readable code, a plethora of Gems, awesome support community. My fav web app language.


  • Tried GitLab, BitBucket, and others - still my fav. Live by their CLI. (In case of fire, git commit; git push; leave building in safe and orderly manner)


  • Want to know everything about your web audience? Insert their javascript into your app and open up a dizzying array of analytical information. I don't see it as an option anymore - table stakes.


  • Tough to build a web app without it. Are you responsive? Are you interactive? If you are, you're using it in some form. Hate it or love it, you need it.


  • A Ruby environment that takes on all the heavy lifting. Install Ruby on Rails, and create a working web app with a single command line. No brainer.


  • Simple caching, tightly tied into Rails. Optimized caching without any work to implement. Done.


  • Tried MongoDB - early euphoria - later dread. Tried MySQL - not bad at all. Found PostgreSQL - will never go back. So much support for this it should be your first choice. Simple local (free) installation, and one-click setup in Heroku - lots of options in terms of pricing/performance combinations.


  • Just like we care about errors, we care about metrics - especially around performance. You'd be crazy not to use it - and not surprisingly, it's a one-click add-on in Heroku.


  • Easy and efficient storage, plus a big set of Ruby Gems that help take any complexity of content management in the cloud. Then turn on CloudFront with your S3 buckets, and boom! Instant CDN.


  • As much as I love AWS EC, I prefer Heroku for apps like this. Heroku has grown up around Rails and Ruby, massive set of add-ons that are usually one-click setup, and I once had to perform an emergency app scale-up a that I completed in seconds from my mobile phone whilst riding the Bangkok subway. Doesn't get much easier than that.


  • In my opinion, the best Content Delivery Network for the money. This, along with other services from AWS's ecosystem make this the easy choice for CDN. Fast, simple and cheap.


  • Have gone from TextMate to Sublime and now to Atom - in love with it - it's open source, it's got a massive contributor community, and it works well. (A bit slow and bogged down with lots of files, but we'll all make it faster over time)


  • Although there are more options out there now, some with better pricing, it was the first and most widely-available tool for sharing content. Our app is asset-heavy (images, videos, icons, etc.) and it makes it dead-easy to move stuff around. Still love it even if it's showing its age.


  • Because it is almost an effortless markup language without ever having to write an HTML tag. Of course, you'll want to use it in environments that make it look pretty (GitHub, etc.)


  • Dead simple automated email workflows for your Rails application.


  • If you care at all about application errors, you should be using this. Hands down.


  • We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.


  • We like CoffeeScript because it's more readable, we use it because we have a lot of libraries and functions already (plays nicely with Rails, too)


  • We offload our background processing tasks (photo sizing, watermarking, etc.) to Sidekiq to keep our app's performance optimal.


1487571

Favorite
Views
30
1487571
Favorite
Views
30