zulhfreelancer

1. Assuming you have multiple Heroku apps and Git remote like so:

development https://git.heroku.com/xxx.git (fetch)
development https://git.heroku.com/xxx.git (push)
origin      git@bitbucket.org:xxx/xxx.git  (fetch)
origin      git@bitbucket.org:xxx/xxx.git  (push)
production  https://git.heroku.com/xxx.git (fetch)
production  https://git.heroku.com/xxx.git (push)
staging https://git.heroku.com/xxx.git (fetch)

sintaxi

List of regions your project is served from when you deploy using surge.

yyz.surge.sh   :   159.203.50.177   :   CA   :   Toronto
jfk.surge.sh   :   159.203.159.100  :   US   :   New York
sfo.surge.sh   :   138.197.235.123  :   US   :   San Francisco
lhr.surge.sh   :   46.101.67.123    :   GB   :   London
ams.surge.sh   :   188.166.132.94   :   NL   :   Amsterdam
fra.surge.sh   :   138.68.112.220   :   DE   :   Frankfurt
sgp.surge.sh   :   139.59.195.30    :   SG   :   Singapore

NicholasTD07

#!/bin/sh
# "Delete all unavailable devices."

xcrun simctl delete unavailable

mwhite

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

rtwomey

Recently, I had a staging database on Heroku that was running on the Ronin database (which was originally the lowest-sized DB you could get at Heroku). Since they added two new options, Crane and Kappa, we wanted to take advantage of the cost savings. Here's how you can migrate your Ronin DB to Crane (or any other plan).

The old database was named BROWN while the new one is CRIMSON. You can determine this by running:

heroku pg:info --app myapp-staging

1. Add Crane database

    heroku addons:add heroku-postgresql:crane --app myapp-staging
   

heroku pg:wait --app myapp-staging

muddylemon

<div class="privacy-policy">

<h1>Privacy Policy</h1>

<section id="privacy-information-we-collect">
    <h3>What information do we collect?</h3>
    <p>We collect information from you when you register on our site, place an order, subscribe to our newsletter, respond to a survey or fill out a form.</p>
    <p>When ordering or registering on our site, as appropriate, you may be asked to enter your: name, e-mail address, mailing address, phone number, credit card information or social security number. You may, however, visit our site anonymously.
    Google, as a third party vendor, uses cookies to serve ads on your site. Google's use of the DART cookie enables it to serve ads to your users based on their visit to your sites and other sites on the Internet. Users may opt out of the use of the DART cookie by visiting the Google ad and content network privacy policy.</p>
</section>