Well, now that I figured out which arangodb was the proper one and used the 
.app bundled version, I have to say, that is quite nice.

Really easy to stand up. This is a hallmark of ArangoDB to me.
This worked more brilliantly than you might know.
Every node was reachable by its internal DNS name. That was fabulous.
As I will use this on test automation nodes, it will mean that most or all 
nodes can ping a series of domains to read and write data, starting with 
localhost. If no localhost, they can go through a known list of peers.
All will have strong perf and strong syncing.
There is a little latency potential when some nodes are across an ocean, but it 
works so far.

Very happy, finally have it working.
Nice touch is, it's also a pretty good example of how to use the .app bundle on 
macOS creatively!
The more I thought about it, the more I realized it makes a lot of sense for 
not only easy deployment, but pretty easy drop in replacement/updation.

Now, I just need to tackle the ssl portion.
(It wasn't ever as easy as RethinkDB)


> On Oct 27, 2017, at 19:26, じょいすじょん <[email protected]> wrote:
> 
> ah, so I see now that is a shell script at
> 
> /Applications/ArangoDB3-CLI.app/Contents/MacOS/arangodb
> 
> doing a few things, but ultimately calling
> 
> /Applications/ArangoDB3-CLI.app/Contents/MacOS/usr/bin/arangodb
> 
> I think I will have some suggestions to put in pull request if you could 
> point me to what files generate the .app bundle in the github repository.
> 
> One of them being that it is unreliable to do this:
> export ROOTDIR="/Applications/ArangoDB3-CLI.app/Contents/MacOS/"
> 
> Mac apps are drag and drop installs and .app bundles should normally be 
> runnable from most locations.
> (Safari is an unusual exception and you cannot run apps from the Trash 
> folder, among others)
> Especially, since the install is drag and drop from a mounted .dmg disk 
> image, users could expect to be able to relocate the bundle to wherever.
> I don't know if this is bash specific, but perhaps
> export ROOTDIR="$(dirname $0)"
> could work more reliably.
> 
>> On Oct 27, 2017, at 18:54, じょいすじょん <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> hmm. It also seems some issues with the arangodb tool at 
>> /Applications/ArangoDB3-CLI.app/Contents/MacOS/arangodb
>> 
>> Every command seems to fail with:
>> 
>> Error: unknown shorthand flag: 'c' in -c
>> 
>> followed by the usage notes.
>> 
>> I was able to reproduce this on multiple machines.
>> Am I doing something wrong there?
>> 
>>> On Oct 27, 2017, at 15:34, Max Neunhöffer <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Hi,
>>> The starter tool arangodb is now contained in the standard distribution and 
>>> we publish precompiled binaries on github. No go language setup is needed.
>>>  Best regards,
>>>    Max
>>> 
>>> Am 27. Oktober 2017 02:40:18 MESZ schrieb "じょいすじょん" 
>>> <[email protected] 
>>> <mailto:[email protected]>>:
>>>> Hi Frank,
>>>> 
>>>> I have a few follow up questions here.
>>>> Does the arangodb cluster tool require a  Go language setup?
>>>> Would you all consider including the cluster tool with the standard
>>>> app?
>>>> Otherwise, would you all consider adding it to various package managers
>>>> 
>>>> like ArangoDB itself is?
>>>> In any case, it might be good to consider renaming the cluster tool to 
>>>> avoid confusion.
>>>> My suggested name would be arangocluster or arangofarm or arangoparty
>>>> or 
>>>> something similarly implying the cluster.
>>>> 
>>>> Is it possible to make each node of the cluster independently
>>>> reachable?
>>>> By this I mean, each node having its own IP/domain in a DNS and then
>>>> each 
>>>> DNS entry being a way to reach the cluster?
>>>> Or each node being directly reachable while being part of the cluster?
>>>> (I will find out soon as I am working on this today)
>>>> 
>>>> 
>>>> On Thursday, April 27, 2017 at 8:02:54 PM UTC+9, Frank Celler wrote:
>>>>> 
>>>>> PS: If you already found the above links on arangodb.com 
>>>>> <http://arangodb.com/> and there
>>>> were 
>>>>> not detailed enough, please let me know.
>>>>> 
>>>>> Am Donnerstag, 27. April 2017 13:01:26 UTC+2 schrieb Frank Celler:
>>>>>> 
>>>>>> A description of the components of the cluster can be found here: 
>>>>>> https://www.arangodb.com/why-arangodb/cluster/ 
>>>>>> <https://www.arangodb.com/why-arangodb/cluster/>
>>>>>> 
>>>>>> The ArangoDB starter provides an easy way to start a cluster: 
>>>>>> https://www.arangodb.com/2016/12/starting-arangodb-cluster-easy-way/ 
>>>>>> <https://www.arangodb.com/2016/12/starting-arangodb-cluster-easy-way/>
>>>>>> 
>>>>>> In your case, you would start e.g. three instances and choose a 
>>>>>> replication factor of 3. This will distribute the data to all three 
>>>>>> servers. What kind of queries do you expect? Is the data updated 
>>>>>> continuously or is it static?
>>>>>> 
>>>>>> An alternative is to use asynchronous replication of a master and
>>>> three 
>>>>>> followers. In that case you must ensure that all write requests are 
>>>>>> directed to the master. Therefore I recommend going cluster.
>>>> However, if 
>>>>>> you need more information about this setup, please let me know.
>>>>>> 
>>>>>> Am Donnerstag, 27. April 2017 12:45:23 UTC+2 schrieb じょいすじょん:
>>>>>>> 
>>>>>>> I need to run instances of ArangoDB on several different Macs.
>>>>>>> They should all have the exact same data.
>>>>>>> To accomplish this I need to understand how to set up replication.
>>>>>>> Are there any tutorials?
>>>>>>> All of these machines have static IPs on a Class A IPv4 network.
>>>>>>> 
>>>>>>> If feasible, I would like to also understand if clustering is a
>>>> better 
>>>>>>> solution?
>>>>>>> It would be nice if they should all be reachable at the same
>>>> address, 
>>>>>>> but not sure how that's a feasible thing without some proxy or
>>>> something.
>>>>>>> 
>>>>>>> Any blog posts or tutorials beyond what I've found at ArangoDB.com 
>>>>>>> <http://arangodb.com/>
>>>> would 
>>>>>>> totally help me out.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> John Joyce
>>>>>>> 
>>>>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "ArangoDB" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/arangodb/HGbsnKK63i0/unsubscribe 
>>> <https://groups.google.com/d/topic/arangodb/HGbsnKK63i0/unsubscribe>.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected] 
>>> <mailto:[email protected]>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to