Our Dev's are asking what are the limitations placed on repositories and I am not finding any solid information. I have found some posts saying it is "basically" unlimited.
Based on this blog: How much data can you put on VSOnline? It’s based on the Blog store and Meta-data store (SQL azure database) and they are increasing, two years ago, the size can be 6.6TB -31.5TB (check the comment)
Related
Our teamwork pipeline uses Google Sheets as a very basic database. We use it because it is a standard spreadsheet that can be accessed online and shared. Based on the exported CSV from this Google sheet, carry out any further analysis.
Since sharing work leads to mistakes, I have to restore the version that makes the mistake without losing the other changes. Since Google Sheets' version history isn't as useful as Git's, I want to put this spreadsheet (ideally, the CSV) under Github version control on an automatic basis.
Would it be possible to do that?
I will need to get into the spreadsheet, export the CSV, and push it to the appropriate repository if I have to do that manually. I think it would be easy to automate. I'm not sure how to do it.
I appreciate your help.
You do not need to export, your spreadsheet can be reached using endpoint as follows
https://docs.google.com/spreadsheets/d/##ssID##/gviz/tq?tqx=out:csv&sheet=##sheetName##
DoltHub is an excellent fit for this use case where you have a spreadsheet being built collaboratively and you want the ability to see the full version history, audit where/when/who each cell's value came from, diff any versions of the spreadsheet, and much more. It's free to use DoltHub and you can easily export your data to CSV from the web, or pull it all down as a Dolt database and access everything locally.
Here's a DoltHub blog post that covers this exact use case in more detail:
https://www.dolthub.com/blog/2022-07-15-so-you-want-spreadsheet-version-control/
If you haven't heard of DoltDB or DoltHub yet, here's a little more background...
DoltDB is the first versioned SQL relational database. It has all the power of a SQL database with all the versioning features of Git. That gives you a database that you can branch and fork, push and pull, merge and diff, just like a Git repository. It's open-source and written from the ground up in Go, and targets full MySQL compliance, so you can use it seamlessly with any tools that connect to a MySQL database.
DoltHub is an online site for finding and collaborating on datasets. The Git-style versioning features built into DoltDB enable easy and safe collaboration and gives you a Pull Request workflow for accepting changes, just like on GitHub. You can control if you want your dataset to be public or private with the free tier, and there's a Pro tier if you need to host private databases larger than 1GB. There's even a DoltLab product available for teams that need to keep their data on their own private network.
There's a very active and friendly DoltHub user community on Discord where the DoltHub dev team hangs out, too, if you have any questions/comments/feedback.
Using Github Enterprise, I have a service/bot account where I'd like to generate a number of Personal Access tokens and provide to a number of teams.
Is there any limit in how many Personal Access Tokens can be generated per user?
As far as I'm aware, there is no limit, but if you want to be sure, you should ask either the GitHub support team or on the GitHub community forums.
GitHub itself has such a bot account and PATs are frequently used there, but do be aware that the UI may be a little (or, depending on how many tokens you issue, very) slow, since it isn't designed for people to have huge numbers of PATs.
You may find it more desirable to use deploy keys if you're accessing a repo, since these have a smaller scope (one repository) and won't have the UI problems mentioned above, but of course that won't work for the API.
I have watched the pricing video here:
https://www.youtube.com/watch?v=tmxXNeqflzM
and have been studying the pricing quote calculator at:
https://licenseandticket.azurewebsites.net/Turnkey/AngularApp#/PriceQuoteWhatIf
How are the following elements defined & quantified?
"Inclusive Add Ons?"
"Better CPU & RAM?"
"Data out from Site?" Does this include large cross-referenced documents stored in a filesystem outside the main database?
"Priority Support?"
"Control Core Deployment?"
"Region Placement?"
"Always On?"
"MDriven Framework Option?"
"History Server Option?"
How does licensing of MDriven designer work if I have the free version (allowing 50 classes) and I want to use more classes? The Turnkey pricing seems to suggest that this is included but how would I unlock the 50 class limit?
Would costs be reduced if I am hosting on my own Azure account?
Finally, how would one calculate the cost for a SaaS where each tenant has their own database?
Many Thanks.
ps: Perhaps it would be a good idea to add this information to the the quote calculator form?
These are all good questions and I will update the wiki page here https://wiki.mdriven.net/index.php/Pricing
I am having a hard time migrating a tfs2017 update 1 to vsts. I am using microsoft's migration guide however I have managed to migrate a single collection and its users and team account into a vsts account (Dry run), but the issue is I cannot seem to find a way to migrate all the other collections into into that particular account, does anyone have faced situation like this or am I doing something wrong here, Or Is it possible or not, if yes then please throw some light on the possibility.
You can't. VSTS only supports one collection per account.
Your options are as follows:
Combine your existing collections into a single collection, then migrate that collection. This may be more or less difficult depending on the amount of data and history you have, and what amount of that you need to retain, and the fidelity at which you wish to retain it.
There is a concept called Organizations that will allow multiple VSTS accounts to be managed underneath a single umbrella, but it's still in preview.
Per the feature timeline, it's slated for third quarter 2017, so sometime this fall.
I have hundreds of thousands of PDFs that are presently stored in the filesystem. I have a custom application that, as an afterthought to its actual purpose, provides access to these PDFs. I would like to take the "storage & retrieval" part out of the custom application and use an OpenSource document storage backend.
Access to the PDF Store should be via a REST API, so that users would not need a custom client for basic document browsing and viewing. Programs that store PDFs should also be able to work via the REST API. They would provide the actual binary or ASCII data plus structured meta data, which could later be used in retrieval.
A typical query for retrieval would be "give me all documents that were created between days X and Y with document types A or B".
My research, whether such a storage backend exists, has come up empty. Do any of you know a system that provides these features? OpenSource preferred, reasonably priced systems considered.
I am not looking for advice on how to "roll my own" using available technologies. Rather, I'm trying to find out whether that can be avoided. Many thanks in advance.
What you describe sounds like a document management or asset management system of which there are many; and many work with PDF files. I have some fleeting experience with commercial offerings such as Xinet (http://www.northplains.com/xinet - now acquired apparently) or Elvis (http://www.elvisdam.com). Both might fit your requirements but they're probably too big and likely too expensive.
Have you looked at Alfresco? This is an open source alternative I came into contact with years ago while being on the board of a selection committee. As far as I remember it definitely goes in the direction of what you are looking for and it is open source so might fit that angle as well: http://www.alfresco.com.