draw.io VS Artifactory

draw.io Reviews

Artifactory Reviews

draw.io mentions (714)

• Reactor controller

  Glad you like it! :D Feel free to reuse/edit it for the Steam page if you want. Also happy to send you the draw.io file if you'd like :). Source: about 1 year ago

• Note taking app

  Shraing, LDAP, sync, reminders are all possible. draw.io can be integrated by an app in nextcloud. Also, there is "Deck" which is a Kanban board for Nextcloud. Source: about 1 year ago

• Diagramming on Note 2 Air+

  I've been using draw.io web to diagram, but I can't find it on android... Is there any good alternatives? Source: about 1 year ago

• Tips and tricks for picking up Visio?

  Visio isnt hard, but stencils are a pain in the ass. So, I suggest draw.io instead, also its free and they have both a cloud GUI tool and desktop tool on Git. I have not used visio since 2019. Source: about 1 year ago

• Creating wiring schematics with ease!

  Adding the desired temperature instead of multiplying by x75 caused my reactor to overheat but maybe I did a mistake in the wiring. :D Why don't you show how you wire your reactor controller by using draw.io with my libraries. ;) You don't have to, of course. Source: about 1 year ago

Artifactory mentions (20)

• Where to store executables shared by a team/project

  I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 11 months ago

• Adding Virtual Environments to Git Repo

  When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago

• Authenticated Docker Hub image pulls in Kubernetes

  Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago

• Concretely, how do you trust the experts? That is, how do you a) identify experts relevant to something and b) determine if they have a consensus (and if so, what it is) on a given topic?

  Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: about 1 year ago

• What do I do with large "asset" files?

  If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago