Search Results

Search found 4 results on 1 pages for 'm1755'.

Page 1/1 | 1 

  • *Best* way to forward/redirect a commonly mis-typed domain name

    - by m1755
    You own thecheesecakefactory.com and your site lives there. You know that many of your visitors will simply type cheesecakefactory.com into their browser, so you purchase that domain as well. What is the cleanest way of handling the redirection. I know GoDaddy offers a "domain forwarding" service but I am not sure if this is the "proper" way of handling it, and I don't necessarily like the idea of GoDaddy handling my DNS. My other option would be sending the domain to my DNS servers and possibly my actual server. Is it possible to do this without setting up a new vhost and a 301 redirect on my server (using DNS only)? If not, how does the GoDaddy forwarding service work?

    Read the article

  • Textmate bundle to remove a directory and build with Jekyll

    - by m1755
    I am looking for a simple Textmate bundle that will do the following two tasks in order: Delete the entire contents (including folders) of a directory (eg. ~/Sites/my_site). Run the jekyll command in the directory of the Textmate project. I am going to associate this with a "save current file" and use it to auto build my Jekyll site into the specified directory each time I save a file inside the project. Notes If #2 isn't possible, then cd into a specified directory and run the jekyll command. Would prefer bash or ruby.

    Read the article

  • Routinely sync a branch to master using git rebase

    - by m1755
    I have a Git repository with a branch that hardly ever changes (nobody else is contributing to it). It is basically the master branch with some code and files stripped out. Having this branch around makes it easy for me to package up a leaner version of my project without having to strip out the code and files manually every time. I have been using git rebase to keep this branch up to date with the master but I always get this warning when I try to push the branch after rebasing: To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes before pushing again. See the 'Note about fast-forwards' section of 'git push --help' for details. I then use git push --force and it works but I feel like this is probably bad practice. I want to keep this branch "in sync" with the master quickly and easily. Is there a better way of handling this task?

    Read the article

1