Changes
no edit summary
** [[Wadsworth]]
* [[Infrastructure:Razor|Razor]]
** LdapLDAP* [[Infrastructure:Milton|Milton]]/[[Infrastructure:Sczi|Sczi]]
** Website
*** Wiki
** git
* [[Infrastructure:Cyberdelia|Cyberdelia]]
** All the above services
** VMs for projects
** other services
*** milton_srv (website files)
[[Infrastructure:Acidburn|Acidburn]] and the website ''must'' be accessible through real services, and it is preferable that [[Infrastructure:Cyberdelia|Cyberdelia]] is too. This means we must use our public IPv4 Addresses allotted by ECE.
=== Other (not all functional) ===
* User websites
** Hosted on [[Infrastructure:Milton|Milton]]/[[Infrastructure:Sczi|Sczi]], so will be public
** Of course, domain owners have to set up their DNS correctly.
* Diaspora*
** use of public or hidden service doesn't matter, assuming it ''can'' be run as a [https://groups.google.com/forum/#!topic/diaspora-discuss/mhAOXarEJuc hidden service].
* [[Iodine]]
** On acidburn. Relies on Acidburn being listed as NS for <code>iod.vtluug.org</code>
* [[Infrastructure:IPsec|IPsec Tunnel]]
** On acidburn
<pre>root@milton:/srv/http/vtluug.org# sudo -u www-data uwsgi --yaml uwsgi.yml</pre>
in a tmux session, to restart [https://uwsgi-docs.readthedocs.org/en/latest/ uWSGI]. It is also
unlikely that nginx will start properly because of weird dependencieson uWSGI, though it can be started with<pre># /etc/init.d/nginx restart</pre>
==== Main Page ====
to provide more information on the set-up, and even with more information, it would be preferable to move
the website to something more simple and sane.
In other words, [[user:echarlie|echarlie]] doesn't want to try to maintain what is in place, but would rather
start from scratch and the existing HTML for the website.
==== Wiki ====
demanded by the Debian package). Postgres is used for the database management, AFAIK, and authentication
is through LDAP. MediaWiki is a dated git version from the stablerepository, as of March 2016, however
updating is more complicated than a git pull. [[user:echarlie|echarlie]] ran a database update in mid-March.
===== Gobblerpedia =====
Uses [[User:andreim|aam]]'s [https://github.com/andreimarcu/linx-server linx], and is an identical implementation to his site
[https://linx.li linx.li]. One of the few sites with a complete startup script. The maintenance is currently the responsibility
of aam, however this is subject to change, pending his retaining root access on sczi.
=== Historically ===
These are VTLUUG services that haven't yet been properly restored:
* foodfor.vtluug.org - For [[Wadsworth]]'s .pickfood and .foodvote commands. This is [[User:Timelord|jpo's]] fault.
* tahoe.vtluug.org - [[user:mjh|mhazinsk's ]] Tahoe-LAFS grid
* git.vtluug.org - git hosting; previously a redirect to gitweb with gitosis as the SSH backend
* gitweb.vtluug.org - git hosting; previously gitweb
* ccdc.vtluug.org - website used for the [[Collegiate Cyber Defense Competition]] in the spring of 2011.
* nagios.vtluug.org - was used for monitoring for a period but not kept up-to-date; the primary issue was that infrastructure, being hosted on the same server, tended to fail all at once
* uniluug.org - deprecated project[[uniluug]]
* security.ece.vt.edu - REDACTED
* wargame.vtluug.org - vtluug's wargame pre-vtcsec
* munin.vtluug.org - former attempt at monitoring
* webchat.vtluug.org - channel webchat; version of the service still runs on the vtluug website as an embeded frame from freenode's website. This should be disabled.
* cdn.vtluug.org - member website
* randynance.info - member website
It would be preferable to keep all existing sites functional. [[user:andreim|Aam]] suggested the use of [https://caddyserver.com/ caddy]
to replace nginx, especially on static sites, because it provides automatic letsencrypt. Most likely, this will not be used, though,in favour of manually configuring letsencrypt (because caddy is not in the repositories).
It is also important to ensure there are '''startup scripts''' for sczi, so that a reboot of it doesn't result in a 10-hour website outage.
==== TLS Encryption ====
All sites should move to automatic letsencrypt certificates within the next few months. letsencrypt is still in beta, but it provides fully functional
and low-hassle 3-month certificates. They will have integration for nginx soon, which will decrease the complexity of getting certs.
