Облако размещает способ пойти для 1 группы разработчиков человека?
Я использовал свой собственный скрипт для создания пакета ipa для специального распространения.
die() {
echo "$*" >&2
exit 1
}
appname='AppName'
config='Ad Hoc Distribution'
sdk='iphoneos3.1.3'
project_dir=$(pwd)
echo using configuration $config
echo updating version number
agvtool bump -all
fullversion="$(agvtool mvers -terse1)($(agvtool vers -terse))"
echo building version $fullversion
xcodebuild -activetarget -configuration "$config" -sdk $sdk build || die "build failed"
echo making ipa...
# packaging
cd build/"$config"-iphoneos || die "no such directory"
rm -rf Payload
rm -f "$appname".*.ipa
mkdir Payload
cp -Rp "$appname.app" Payload/
if [ -f "$project_dir"/iTunesArtwork ] ; then
cp -f "$project_dir"/iTunesArtwork Payload/iTunesArtwork
fi
ipaname="$appname.$fullversion.$(date -u +%Y%m%d%H%M%S).ipa"
zip -r $ipaname Payload
echo finished making $ipaname
Скрипт также увеличивает номер версии. Вы можете удалить эту часть, если она не нужна. Надеюсь, это поможет.
2 ответа
There are very different kinds of cloud hosting, and the answer depends on which kind of hosting you are talking about.
One excellent resource is the second half of this presentation.
I will oversimplify and classify them into two extremes: hosting services that just provide you with a virtual machine (VM) such as Amazon's EC2, and those that provide you with an application environment such as Google's AppEngine.
Thinking first about the VM approach, I would say that for a small "1 man show", I really wouldn't worry much about the scaling problem: it won't matter unless you are successful, and so you're better off taking the Twitter approach and working on being successful, then dealing with scaling later. Sure, it will come back to bite you later, but only if you ARE successful. Worry about designing a scalable ARCHITECTURE, but don't bother with scalable HARDWARE.
Even with that proviso, using EC2 or some other cloud hosting can be a good idea. It means you are paying someone else to worry about electric bills, purchasing of hardware, network connectivity, system maintenance, and things like that. And this person is probably cheaper than YOUR TIME unless you have experience as a professional sysadmin (or a friend who you can pay in smiles and stock).
The entire way to think about it changes if you consider something like Google's AppEngine. (NOTE: given that it's a .NET MVC web application, that probably isn't an option for you. I'll explain the pros and cons anyhow.) This changes the entire way you architect your application, and it means that you are effectively tied to this host (or at least this kind of hosting) forever (or until you do a complete-from-scratch rewrite of your system... don't make any plans that rely on doing that!). In the long run, that may be bad or good, it's kind of hard to tell right now. But you can't beat the startup costs: from Google it's FREE until you get up to traffic sizes that ought to be bringing in some profit. It's really hard to beat FREE for all hosting AND operating expenses, so I think some small, 1-man shops will be taking this route in the future.
On the whole, I advise using cloud based hosting simply because if you want to be a success you need to focus like a laser on the one thing you do well; whatever that is, it probably isn't system administration.
Значительным преимуществом может быть экономия средств при некоторых обстоятельствах.
Предположим, вам требуется совместное размещение резервного центра обработки данных, который может «сработать» в случае стихийного бедствия или отключения электроэнергии. Обслуживание двух наборов серверов в двух местах может быть непомерно дорогим. Если облако уже предлагает такого рода резервирование от сбоев, оно может со временем сэкономить довольно много денег.