I'm also in the beta, and I like it a lot. It's functionally equivalent to `dlite`, which Nathan LaFreniere has done an extremely good job on. He deserves massive credit for making OSX Docker dev bearable and for providing the inspiration for 'Docker for Mac'. A few issues I've seen: 1. I cannot believe they are using `docker.local`. This hostname will cause nothing but trouble for years to come. DON'T USE `.local`! Apple has decided that `.local` belongs to Bonjour, and due to a longstanding bug with their IPv6 integration, you can expect to see a 5-10s random delay in your applications as Bonjour searches your local network to try to resolve `docker.local`. Yeah, you put it in your `/etc/hosts`? Doesn't matter. Still screws up. Use `docker.dev` or `local.docker`. -beta8 is screwed up. It won't bind to its local ip anymore. Excel autosave folder location. AutoSave is a different feature which automatically saves your file as you work - just like if you save the file manually - so that you don't have to worry about saving on the go. On the Mac, AutoSave is available in Excel, Word, and PowerPoint for Office 365 subscribers. Some developers recommend to use the docker-sync which can synchronise the files on the local machine to docker container realtime. But I prefer another workaround which allow you to update the files directly read by docker container. And it does not need to create xml file for configurations. Docker for Mac is the current release of Docker for OSX. Requirements: Mac must be 2010 or new model with Intel's hardare support for memory management unit (MMU, virtualization, and Unrestricted mode. The only option is to port forward from localhost. Unfortunately, Docker isn't offering a download of beta7. It boasts improved speed, and we wouldn’t be surprised if it were faster than HFSExplorer. Just install it, and Mac drives will show up like any other drive. If you need to work with Mac-formatted drives on a regular basis and you want the operating system integration, speed, and write access, Paragon HFS+ is a great choice and will be worth it for you. And, unlike HFSExplorer, it offers full read/write access to Mac-formatted drives, so you can write to them from within Windows. Thankfully, I still had the DMG around. The polish is still lacking. Most menu bar items ask you to open up something else. Why 'Docker for Mac'? Couldn't the team think of a less confusing name? Now I have 'Docker' running 'docker'. Otherwise - great projects, and again, much credit to @nlf for `dlite`. If you're not part of the beta, check out dlite (). It's at least as good as Docker for Mac. > I cannot believe they are using `docker.local`. This hostname will cause nothing but trouble for years to come. We are indeed moving away from `docker.local` in Docker for Mac. There have actually been two networking modes in there since the early betas: the first one uses the OSX vmnet framework to give your container a bridged DHCP lease ('nat' mode), and the second one dynamically translates Linux container traffic into OSX socket calls ('hostnet' or VPN compatibility mode). Try to give hostnet mode a try by selecting 'VPN compatibility' from the UI. This will bind containers to `localhost` on your Mac instead of `docker.local` and also let you publish your ports to the external network. One of our design goals has been to run Docker for Mac as sandboxed as possible, and so we cannot just modify the /etc/resolv.conf to introduce new system domains such as '.dev'. We've been iterating on the networking modes in the early betas to get this right, so beta9 should hopefully strike a good balance with its defaults. It's also why we've been holding a private beta, so that we can make these kinds of changes without disrupting huge numbers of users' workflows. Your feedback as we figure it out is very much appreciated! Easycap usb 2.0 mac software. Interesting, this is the first time I'm reading about it [1]. Well, if anything it looks like a web app would have to be rebuilt from the ground up to fit that model. I haven't yet read much about it, but here's a few questions that pop up immediately: 1) If you have a container per data object, doesn't that mean you also have to start a process every time a user opens a document? So forget about doing any computations in the setup. Even just things like using regex patterns in python (that need to be compiled once) or using anything with a VM (that needs to be started) you'd have to give up. Usecase seems to be extremely limited, but maybe I'm not getting something right here. 2) How do you handle indexes, views and collections over a large set of data objects? > it looks like a web app would have to be rebuilt from the ground up to fit that model. The app market is full of apps that were not originally written for Sandstorm: Examples: Wekan, Etherpad, Rocket.Chat, EtherCalc, draw.io, Gogs, Dillinger, NodeBB, EtherDraw. It turns out that converting a web app to Sandstorm is mostly deleting code. You delete your user management, your collection management, your access control, etc. What you have left is the essence of your app -- the UX for manipulating your core data model, of which you now only need to worry about one instance. > doesn't that mean you also have to start a process every time a user opens a document? Most apps we've encountered only take a couple seconds to start. But we're working on a trick where we snapshot the process after startup and start each grain from the snapshot, thus essentially optimizing away any startup-time slowness. > How do you handle indexes, views and collections over a large set of data objects?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |