Hacker News new | ask | show | jobs
by krotik 3570 days ago
Hmm, I would like to provide a demo. For now I host the GOPATH structure on github, which includes a demo, while the code which you get via "go get" is on a self hosted server. So you can write:

go get -d devt.de/common devt.de/dudeldu

if you want just the source (vendor form) or you can:

git clone https://github.com/krotik/dudeldu/ .

if you want it with a demo. You can then build the executable and run it with the demo folder.

I use a self hosted machine to run the build and unit tests overnight. I know the vast majority of Go projects does it differently - I am still unsure but so far it worked for me ...
1 comments
speps 3570 days ago
The demo should really be in a separate repo and then you can link to it in the README.
link
krotik 3570 days ago
Yes, I could host the demo on my server and move the code to the root directory. However, I am not sure about the benefit.

In my understanding the main reason why people put code in the root is so that you can use "go get" to do a checkout. "Go get" then creates a src dir and puts the code there. This functionality is already covered by my server. Since my code path uses devt.de "go get" will always use my server and not github.

The only way someone could use the github code would be with "git clone" and here I think the src dir in the repo might be useful. Otherwise, you have to make sure to create this yourself.

Am I missing something?

link
eriknstr 3570 days ago
Personal servers are more prone to intermittent operation, caused by things such as an OS upgrade gone bad and the owner not finding the time at the moment to fix it. If on the other hand you have a repo on GitHub that one can go get then users will know with much greater confidence that the repo will stay available at all times for the foreseeable future.

I run my own web and mail servers, but the canonical repositories for all my code is on GitHub, both because then I know my code is always available to myself but also because I know that it means that others will have fewer reasons not to use my projects, because even though I know that my uptime and stability is good, others can't know that, but they know that GitHub is.

link