SystemAdministration-OLD-2024: Difference between revisions
Jump to navigation
Jump to search
Mechanicjay (talk | contribs) |
Mechanicjay (talk | contribs) |
||
| Line 27: | Line 27: | ||
==Work Notes== | ==Work Notes== | ||
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file [[soylent-services]] with bind and having external services handle serving out our dns. | |||
==Resources== | ==Resources== | ||
Revision as of 21:33, 15 March 2014
TeamPages - parent, Development
Welcome
Who we are
- robinld -- systems
- mechanicjay -- systems
Index of Development Pages and Resources
Servers
- soylent-www - Primary Apache and slash server for main site.
- soylent-db -- mysql server, holds the slash database
- slashcott - Holds the slashcott site, development machine
- soylent-services - mail, wiki, other services as needed
Known Problems
- There is debugging code enabled in the init script for varnish that is specifically labeled 'DEBUG CODE DON'T ENABLE IN PRODUCTION' -- Mechanicjay notes that we had intended to turn this off after the first week as it was helping us troubleshoot login problems the first week. Mechanicjay further notes that he no longer seems to have ssh access to soylent-www so has been unable to comment this out of the varnish config.
- There are errors in the zone file in the spf TXT record
- No init script for Apache.
- Broken https configuration
- Nginx running
Work Notes
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file soylent-services with bind and having external services handle serving out our dns.
Resources
- DnsRecords - copy of the zone file pasted from the machine that was accidentally turn off
- EmergencyProcedures - in case of fire, break glass (Red befor messing with servers)