The one project - multiple repositories is a design choice we made right from the beginning since it follows more naturally how work is done in actual companies, e.g. there are projects and in a project, there are frontend, backend, and other repositories. Finding all the stuff from one place is quite convenient.
Mentioning Europe hosting here is more like a marketing thing I agree, but hey, you need to distinguish yourself somehow. In addition, we are targeting European markets at the moment, so whatever relates to that is worth mentioning, right?
Also, we have been dealing with companies of different sizes for the last decade. During that time we have learned that there are legislations and such, that dictate where some code needs to be hosted. There are also people who are security constrained because of no apparent reason and want certain things, such as their code being hosted in Europe rather than in US.
The latencies might also contribute to the operations in the web UI in some cases. Anyway, it's not our biggest marketing message, but something I wanted to mention.
Thanks for your comments so far. I would love to hear more feedback from you after you have tried the product.
At the moment no I'm afraid. Probably it could configurable. Would you like to submit this at http://support.deveo.com/ so we can follow up with you when it's done?
We are trying out new business model. Limited supply for now. Get it while it lasts. :) Comments, questions, etc. welcome. Will be checking this thread.
We have solved this in Deveo by grouping repositories inside projects since it reflects more naturally how software is built outside the open source community. This has been our focus from the inception. In non-open-source projects, a project typically includes multiple repositories (such as backend and frontend at least), and they all share the same issue tracking and wiki functionalities.
We covered this topic and other differences between Deveo, GitLab and Bitbucket recently in a blog post. If you are interested to see an alternative viewpoint on things, check http://blog.deveo.com/what-makes-deveo-different-from-github... - I would love to hear feedback whether our approach is viable compared to GitHub's open-source approach on things.
Thanks for your comment. I fully agree that there are many companies who want to host the development tools behind-the-firwall, and luckily Deveo can be hosted on-premises as well as used from the multi-tenant cloud instance. Actually, our biggest customers use solely the on-premises version, which scales to thousands of users using clustering and load balancing. The article tackles the things from the SaaS point of view because more and more companies are moving to the cloud. I need to clarify that Deveo can be used also behind the firewall in the future more.
All of the "developer focused" features you mentioned are present in Deveo. Rhodecode, on the other hand, lacks two fundamental features to support the daily workflow of developers: Issue tracking and Wikis. These two functionalities are present in Deveo, GitHub, GitLab and Bitbucket.
If you wish to compare the differences between Deveo and Rhodecode, head on to https://deveo.com/trial and see the differences yourself. I would love to hear what you think after you have actually tested it.
comments and questions welcome. will be monitoring this thread.