This guide is has moved to https://epicserve-docs.readthedocs.org/en/latest/django/ubuntu-server-django-guide.html.
This is a post by Joel Spolsky. The original post is linked at the bottom.
This is such a common question here and elsewhere that I will attempt to write the world's most canonical answer to this question. Hopefully in the future when someone on answers.onstartups asks how to split up the ownership of their new company, you can simply point to this answer.
The most important principle: Fairness, and the perception of fairness, is much more valuable than owning a large stake. Almost everything that can go wrong in a startup will go wrong, and one of the biggest things that can go wrong is huge, angry, shouting matches between the founders as to who worked harder, who owns more, whose idea was it anyway, etc. That is why I would always rather split a new company 50-50 with a friend than insist on owning 60% because "it was my idea," or because "I was more experienced" or anything else. Why? Because if I split the company 60-40, the company is going to fail when we argue ourselves to death. And if you ju
Welcome!
UPDATE: This list is no longer maintained. I've moved it to its own repo so you can send suggestions as Pull Requests. https://github.com/dideler/bootstrapping/
For feedback or suggestions, please send a tweet (@dideler). Gist comments don't notify me. Pull requests aren't possible with gists (yet), so I don't recommend forking because then I can't easily get the change.
Starring this gist will give me an idea of how many people consider this list useful.
This article is now published on my website: Prefer Subshells for Context.
We love solving puzzles at Priceonomics. We also like meeting people who like to solve puzzles. Here are two interesting puzzles we've faced at some point in the past months that we'd like to share with you.
If you have any questions, contact omar@priceonomics.com.
Author: Michael van Rooijen (@mrrooijen)
DISCLAIMER: I am a programmer, not a sysadmin in my day-to-day life. I provide this guide simply as a self-reference, and as a way to contribute to the community of developers. The main motivation for writing this guide is because of the lack of properly written guides/tutorials. They were either out-dated, inaccurate, in a non-English language or simply too vague to understand (at least for me, as a programmer and not a sysadmin).
I hope this guide helps getting you up and running with your own collection of VPS's on your own Dedicated Server over at Hetzner.de.
Requirements:
armv5te-android-gcc armv5te-linux-rvct armv5te-linux-gcc | |
armv5te-none-rvct | |
armv6-darwin-gcc armv6-linux-rvct armv6-linux-gcc | |
armv6-none-rvct | |
armv7-android-gcc armv7-darwin-gcc armv7-linux-rvct | |
armv7-linux-gcc armv7-none-rvct | |
mips32-linux-gcc | |
ppc32-darwin8-gcc ppc32-darwin9-gcc ppc32-linux-gcc | |
ppc64-darwin8-gcc ppc64-darwin9-gcc ppc64-linux-gcc | |
sparc-solaris-gcc |
Over the last 3 years or so I've helped a bunch of companies, small and large, switch to Django. As part of that, I've done a lot of teaching Django (and Python) to people new to the platform (and language). I'd estimate I've trained something around 200-250 people so far. These aren't people new to programming — indeed, almost all of them are were currently employed as software developers — but they were new to Python, or to Django, or to web development, or all three.
In doing so, I've observed some patterns about what works and what doesn't. Many (most) of the failings have been my own pedagogical failings, but as I've honed my coursework and my skill I'm seeing, time and again, certain ways that Django makes itself difficult to certain groups of users.
This document is my attempt at organizing some notes around what ways different groups struggle. It's not particularly actionable — I'm not making any arguments about what Django should or shouldn't do (at least
# Python virtual env alias | |
alias activate='test -d ENV && source ./ENV/bin/activate || echo "No Virtualenv in the current folder"' | |
alias mkenv='test -d ENV && echo "Already exists" || virtualenv --system-site-packages ENV; activate' |