-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document neurogitea #117
Comments
Between @mguaypaq, @joshuacwnewton and @namgo who is up for this? |
I'm not sure if I'm the best person to update the docs, given that I'm working from Ontario and thus only have VPN access (and at the moment, there seem to be issues with connecting to the web UI via VPN). 😓 |
I guess I'm the most likely candidate, since I deal with |
I did a first pass in #124. |
Looks like upstream has finally opened port 80 for us, so accessing the web gui is now possible without the port-forwarding solution! We should probably update our docs to reflect this. |
omg port 80!!! Did you get port 443 too? I never thought it would happen. That ticket outlasted me. With port 80 and 443 open you can switch to using letsencrypt and also get rid of the cert warning! I hope it treats you well!! |
I'm not sure we can use letsencrypt, I think ports 80 and 443 are only unblocked from wifi and the VPN at the moment. |
😭 |
https://github.com/neuropoly/intranet.neuro.polymtl.ca/edit/master/data/git-datasets.md needs work since https://github.com/neuropoly/computers/issues/457 replaced gitolite with gitea.
Some of that is still useful and valid, like the parts about generating an ssh key, but most should go.
The part about making a new repo should be replaced by a pointer to https://data.neuro.polymtl.ca/datasets/template/ with this screenshot:
it probably needs other work too
The text was updated successfully, but these errors were encountered: