I see people looking for a private Jamulus server ready to use. I may help if you do not have the technical skills to create one.
I have been playing with the software for a while and am now able to deploy Jamulus servers almost anywhere on the planet to provide good latency for anyone on earth. Don’t worry I’m staying home :)
Simply contact me at martin.jamcloud@gmail.com
Best,
Martin Pernollet
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
<opinion>
maybe it would be better to make a wiki or a youtube video that describes how to do this, this reduces you as "Single Point Of Failure", because the people that would use your service would be lost if they can not reach you anymore...
</opinion>
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My proposal is to help people without technical skills to run private servers for them.
As I received questions about setting up private servers by themselves, I have updated the wiki here with these questions to avoid behing a point of failure :)
The page you have put these on relates to both private AND public server modes, so they may be confusing if people read them without the expectation of creating a private server and before they read the page explaining the types. There is a separte page for private servers, so to remove the confusion I'll move those questions there if that's OK.
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Agree. I just wanted to add Q&A where existing Q&A stand. Maybe we should move all Q&A in a F.A.Q. page with sections related to Client, Public Servers, Private Servers, etc?
By the way your diagrams in the "choosing server type" are excellent. I am thinking just now that maybe we should add a private server schema where the private server is NOT running on one of the client computer but on internet (but not registered on the public server catalog).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes - now that we have some actual frequently asked questions building up, we should probably has a proper FAQ section. This should get firmed up more with the results of the user survey that's live right now. I'll see if I can put a FAQ page soon.
On your point about a diagram for an external private server: I thought about that, but concluded that anyone competant enough the run a server externally to their network (and that can be public server too of course) would easily grasp the concept by looking at the "Private Server" diagram. The problem with diagrams is that they are a bitch to maintain, and the more you have the harder it is, so I'm a bit reluctant to introduce another one. This applies to the rest of the docs in fact, which need to be regularly checked to make sure we're not saying something in more than one place that might need to change later :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK thanks. I've linked it up to the main navigation and attempted to chunk it into sections so that it doesn't get too confusing.
The main problem with a single FAQ page that covers servers and clients (and also don't forget that not everyone understands what a "client" is) is the server modes issue: unless people understand the modes before they start setting up a server, they can become confused very quickly (I notice several of the FAQ entries were basically down to people not undertanding the difference between public and private). This is why the docs are structured to encourage people to read them linarly if possible, and tries to separate out to the two concepts. A single FAQ page increases the possiblity of confusion there I think.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree with you. I think it would be better to split the documentation in three documentations Musician Guide System Administrator Guide
* Developer Guide
With this in mind it might easier to rewrite the summary first to ensure a "linear consistency", and then add content into it. It would be easier to read than the current documentation that is full of usefull information but sometime messy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did also Terry said "... tell a man that he can get electricity at home with a cheap monthly subscription and he will probably stop hitting flints" ? :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone,
I see people looking for a private Jamulus server ready to use. I may help if you do not have the technical skills to create one.
I have been playing with the software for a while and am now able to deploy Jamulus servers almost anywhere on the planet to provide good latency for anyone on earth. Don’t worry I’m staying home :)
Simply contact me at martin.jamcloud@gmail.com
Best,
Martin Pernollet
<opinion>
maybe it would be better to make a wiki or a youtube video that describes how to do this, this reduces you as "Single Point Of Failure", because the people that would use your service would be lost if they can not reach you anymore...
</opinion>
Hi Marc,
Indeed! There is already a public documentation explaining how to setup a private server here
https://github.com/corrados/jamulus/wiki/Running-a-Private-Server
My proposal is to help people without technical skills to run private servers for them.
As I received questions about setting up private servers by themselves, I have updated the wiki here with these questions to avoid behing a point of failure :)
https://github.com/corrados/jamulus/wiki/Running-a-Server
Hi Marc - good stuff!
The page you have put these on relates to both private AND public server modes, so they may be confusing if people read them without the expectation of creating a private server and before they read the page explaining the types. There is a separte page for private servers, so to remove the confusion I'll move those questions there if that's OK.
Agree. I just wanted to add Q&A where existing Q&A stand. Maybe we should move all Q&A in a F.A.Q. page with sections related to Client, Public Servers, Private Servers, etc?
By the way your diagrams in the "choosing server type" are excellent. I am thinking just now that maybe we should add a private server schema where the private server is NOT running on one of the client computer but on internet (but not registered on the public server catalog).
Yes - now that we have some actual frequently asked questions building up, we should probably has a proper FAQ section. This should get firmed up more with the results of the user survey that's live right now. I'll see if I can put a FAQ page soon.
On your point about a diagram for an external private server: I thought about that, but concluded that anyone competant enough the run a server externally to their network (and that can be public server too of course) would easily grasp the concept by looking at the "Private Server" diagram. The problem with diagrams is that they are a bitch to maintain, and the more you have the harder it is, so I'm a bit reluctant to introduce another one. This applies to the rest of the docs in fact, which need to be regularly checked to make sure we're not saying something in more than one place that might need to change later :-)
Yes! Refactoring the documentation regularly is important. I just created the FAQ page.
OK thanks. I've linked it up to the main navigation and attempted to chunk it into sections so that it doesn't get too confusing.
The main problem with a single FAQ page that covers servers and clients (and also don't forget that not everyone understands what a "client" is) is the server modes issue: unless people understand the modes before they start setting up a server, they can become confused very quickly (I notice several of the FAQ entries were basically down to people not undertanding the difference between public and private). This is why the docs are structured to encourage people to read them linarly if possible, and tries to separate out to the two concepts. A single FAQ page increases the possiblity of confusion there I think.
I agree with you. I think it would be better to split the documentation in three documentations
Musician Guide
System Administrator Guide
* Developer Guide
With this in mind it might easier to rewrite the summary first to ensure a "linear consistency", and then add content into it. It would be easier to read than the current documentation that is full of usefull information but sometime messy.
i always try to transfer the knowledge as terry pratched said:
Give a man fire and he has warm for a night, teach a man how to make fire and he is warm for the rest of his live...
Did also Terry said "... tell a man that he can get electricity at home with a cheap monthly subscription and he will probably stop hitting flints" ? :)