Hello All
I am writing this today in curiosity in what you all look for in webhostign for your development projects
I am considering setting up a Hosting company in the mind to provide for all xda/smartphone developers
I am all ready thinking that offering the ability to have unlimited bandwidth would be an advantage but i need to check on how well i can offer this with the size of roms coming i may offer separate package were allowing file distribution and in that allow developers to run a cook your own rom
but apart from basic webhsotign needs what would you developers look for in hosting if it was specifically tailored for your selfs (personal git repos, svn repos, domain regitrations)
But tell me what youd want from hosting tailored to a smartphone developers needs
Related
Hi all-
I didn't find anything in the wiki, and I couldn't find a directly-related forum- where would I look for or ask programmers about having a custom app built for a mid-size company that will need ~40-100 users?
We have an existing app on the Blackberry but as we are looking to switch to Android later this year, the BB developer has told us outright they do not intend to port or build for Android. :silly:
It is fairly basic functionality similar to that seen in numerous other Android apps; but these existing Android developers want tens of thousands of dollars to make simple modifications to their functionality. So I'd like to investigate whether we could just have something built from scratch ourselves, and then we own it outright.
I have the support of a major enterprise CDN company to help open source projects and developers with free unlimited CDN hosting.
A few questions would help me figure out how to start.
Do you have issues with distributing your work at the moment?
Would you be interested to use a CDN to distribute your work? (roms/mods/themes..)
What is the average filesize of the files you plan to host?
What is the total amount of storage you would need?
How much traffic can you generate in a month?
What would be your preferred method of upload? (ftp/rsync/web)
What other features you would like to see?
The only thing needed from you would be to put a few links somewhere, mention the project or even add a banner.
Tell me your thoughts on this.
Thanks
Time to shift my attention towards other things:
Hosting for developers.
Are you an Android Developer in need of a stable, speedy server that is available 24/7, AND allows you to build full websites dedicated to you, your team, and your ROM? Look no further.
I intend to create a server that will allow developers (and perhaps users) to host their ROM. It won't be some pre-formatted stuff either. It will be a full-on custom website with FTP access, and SSH access in the future. You'd have unlimited bandwidth, upload/download speed, unlimited options to create folders for yourself, and lots more.
However, I want this to run off of donations, just as most other sites do. There will be no ads, and no dumb wait times. Just pure speed and ease of access.
The reason why I'd like this to run off of donations is to ensure that I keep this site ad-free, and because such an amazing service is being offered to basically any developer out there, regardless of whether or not we have had clashes and arguments in the past.
To get this thing off of the ground, I'm going to need about 20$ USD to start, and about the same price per month minimum. That's it. I will never put up large banners asking you to donate, or anything in excess. I just want this to be an awesome experience for developers and users alike, allthewhile teaching me a multitude of news things.
If you're interested in donating to get this off the ground and in turn get a guaranteed spot, please comment below, and I will give you the information you need.
If you have any questions or think I'm a POS, please don't be afraid to ask or let me know as well.
- Kyler
This is NOT meant to discredit any other Android hosting sites.
Oh yeah!
I'd also use any 'extra' donation money towards saving up for dedicated servers, and improving the sites security. If I had a plethora ("safe amount") of extra donation money, it would go towards adding useful features to the site.
Hi guys!
I had this thought recently when using my mediafire account- it sucks... probably it doesn't suck more than average filehosting account, but still...
The idea (in fact two of them) I came up is the following:
Distribute evrything via bittorrent
For now I can't see any major downsides of the concept - but I think it'll be most useful for bigger distributions that build daily builds and/or support many phones. It could considerably ease the load on their uplinks thanks to the way bt works.
How I imagine it to work:
The person who would like to contribute would downoad the client, install it on his server/pc, register to the central repository, and in the end set a few config options (bandwidth he wants to contribute, how much disk space, and to what projects/phones/developers) and that's it. The client would then ask the central repo for some torrents to mirror and it'll run by itself (periodically asking the repo for new downloads or removals) - hopefully without any maintanance ever needed.
I imagine "the client" to be as simple as possible - maybe even a one shell script using curl to communicate with the repo. And of course some torrent client - if the project develops, support for many clients (and windows) can be added.
The server would do all the thinking as it'd have the most complete information about the entire "pool" - how much space is available to which projects, how many dowloads of each torrent there are etc. so it'd be easier for it to decide who should mirror what (of course within their defined filters). But in the beginning I don't think it would have to be very complicated either - if more clients connect, the algorithm can be made smarter.
The thing is - many of your users would be happy to contribute in some way to rom development, but usually they lack the skill necessary. But they could contribute hardware/bandwidth, especially that it doesn't require any effort from them and gives them the satisfaction of contributing.
The other thing is distributed build system based on similar principles: provide people with a configured VM image of a building system for various virtualization technologies and operating systems and that's it. The initial setup would be made as simple as possible for the end user. Having one vmimage would guarantee that everybody has consistent build environments.
This would of course be useful only to large android rom distributions that support multiple devices - building 20+ nightlies/a day (and distributing them) can be quite a challenge and requires considerable processing power and bandwidth, but if they had a farm of build servers (even small), this wouldn't be a problem and they could commit their hardware for pure development/debuging efforts.
Of course the system would inform the developer if his build failed somewhere and provided a log, so that he (or a person responsible) can investigate. The system could also do some automated recovery, i.e.: build fails -> clean ccache and rebuild, if fails, restart on another machine and if this fails, inform the developer. The system could also detect a faulty build machine (that fails some builds that run successfuly elsewhere) and exclude it from the pool (and of course send an email to machine owner). And of course ready builds would be reported to the repo server and distributed via torrent.
The whole trick is that for both distribution and compilation none individual contribution has to be large - users can dedicate 1GB of mirror space and it'll allow to host 4-5 rom builds. For build machines, they don't need to have a 6-core monster because it doesn't matter if it builds 1,2 or 3 hours as long as it builds (my 4x3.2GHz machine builds a rom in <90mins). What's more, they don't have to run those severs 24/7 - the system will know which machines are always on and which are not and distribute the load taking this information into account.
When the community grows beyond some critical mass, the system will work despite people droping in and out of the "grid"...
Just a loose idea... Tell me what you think.
Kodi™ Foundation are ready to end Android support and development !!
ARE YOU ????
Call out for developers
As you may or may not know is that Kodi is maintained by a group of volunteers since its first inception dating back to the original XBOX days. Over the years many volunteers have spent countless days if not months on every aspects of what makes Kodi great. This consist of writing and maintaining the code base of Kodi, expanding to new platforms, maintaining the forum, wiki, website and download server and more……
So why do we need you? Well the fact is that over the years the core team of Kodi has remained about the same size while the amount of users went from couple of thousand to many, many millions. Not forgetting the fact that it went from only a XBOX application to what is now running on Linux, Windows, iOS, OSX, Android. All this still with the same amount of people. Now comes the time that we will actually start calling out for some help. To put it simple we want to ensure that Kodi remains alive on all platforms while at the same time lowering the support burden each developer now faces these days. Each of the core developers has his own specialty and since Kodi is quite big you quickly run out of developers that know enough of certain sections. Add to that the changes needed for each operating system upgrade that happens and all the problems that arise with that.
To put it in perspective we basically have only 1 developer for each section or even complete platform. As already mentioned the entire team consists of volunteers which means everything is done in their spare time next to having an actual day time job and a personal life. This results in having only a few hours at most to spend on what they see as their hobby which i can say they are passionate about.*Over the years the team consisted of many different developers who gave all they could but due to whatever reason had to change priorities which resulted in not spending time in Kodi anymore.
So in short what we are looking for are C/C++ developers who are willing to put in some of their spare time in maintaining and improving our core code. This can either be doing some minor bugfixing, reviewing existing pull requests for code contributions or even creating some of their own code refactoring or feature additions. It really doesn’t matter if you are just a student just starting out on C/C++ or are already a senior programmer. We would welcome anyone who is willing to do their part on any improvement that is needed. A fair warning is that our codebase isn’t for the faint hearted as it’s quite massive and we are quite strict regarding code review before we merge anything. However don’t let this frighten you off as our current (or outside developers) will certainly give you pointers on improvements to get it included.
What we currently need most are developers with knowledge of the following components to improve current implementations:
• Windows DirectX11 / audio / video•*Android NDK / audio / video• iOS & OSX / audio / video• General knowledge of C/C++ and willing to do some coding in areas of their interest.
Any bugfix can be send to our main github code repository for review straight away. If you are not sure or want to take on a bigger task or change feel free to open up a thread on our forum where you write down your proposal to get some initial feedback.
Wiki pages to get you started:*http://kodi.wiki/view/Development
Forum:*Developer sucbsection
Code on Github:*https://github.com/xbmc/xbmc
Regards As Always